The practical answer
For many air receivers, the practical pathway is: identify the item, confirm pressure and volume, classify the hazard level under AS 4343, and then determine what design, registration and in-service requirements flow from that classification in the relevant jurisdiction.
An old or modified receiver can be harder than a new one because the nameplate may be incomplete, the original design code may be unclear and the actual service conditions may have changed.
The engineering value is often in reconstructing a defensible equipment record before anyone tries to decide whether the receiver can remain in service, needs registration, or needs further assessment.
Air receiver registration pathway
Before deciding whether registration applies, build a dependable pressure-equipment record from the nameplate, design data and hazard-level inputs.
How to use this summary
- Do not start with a guessed tank size — start with the nameplate and design data.
- If pressure, volume or hazard-level inputs are uncertain, reconstruct the equipment record first.
- Poor history, repairs or visible changes justify integrity review before relying on the current basis.
- Once the inputs are sound, run the Schedule 5 registration pathway instead of guessing from appearance.
The full registration check handles the actual legal branches and exceptions.
When this question usually matters
A used compressor package or loose air receiver is being installed at a new site.
The receiver has no clear register number or compliance file.
An existing plant item is being altered, repaired or relocated.
An inspection, audit or insurer question has triggered a record review.
Red flags that make the question more significant
No readable nameplate or uncertain maximum allowable pressure.
Visible modifications such as new nozzles, patched areas or undocumented support changes.
The receiver is close to hazard-level boundaries and the volume or pressure data are uncertain.
No inspection history is available.
The receiver is being used under conditions that differ from the original package information.
How to screen the registration question
The first objective is to build a dependable equipment file. Registration cannot be answered confidently from photographs alone.
Identify the equipment and service
Confirm that the item is an air receiver or related pressure vessel, what compressed medium it contains and how it is actually used on site.
Recover key design data
Record design pressure, volume, temperature, manufacturer, serial number, design code and nameplate details if available.
Classify the hazard level
Use reliable pressure, volume and fluid inputs to determine the hazard-level pathway instead of estimating from overall tank size.
Check the jurisdictional compliance basis
Assess what registration, design verification, inspection or record requirements flow from the equipment classification and local regulator rules.
Resolve uncertainties before continued service
If the basis is unclear, determine whether the item needs further engineering assessment, inspection, temporary restrictions or replacement.
Detailed practical examples
These examples show how the question changes a real engineering decision. They are not universal answers; they show what needs to be clarified before the right answer becomes obvious.
Used air receiver purchased without a complete dossier
A workshop purchases a used compressor skid. The receiver has a partly legible nameplate, no obvious compliance folder and an uncertain service history.
This is the classic situation where teams want a yes/no registration answer immediately, but the real job is reconstructing the design and hazard-level basis first.
What made the job difficult
- The pressure rating appears on the plate, but the internal volume is uncertain.
- No one can confirm whether the vessel has been modified or repaired.
- There is no inspection history bundled with the purchase.
How the review should proceed
- Capture and verify all nameplate information, dimensions and evidence of package configuration.
- Estimate volume only using a defendable method and note the confidence level of the data.
- Determine the hazard-level pathway and then review what that implies for continued use and any registration questions.
- If uncertainty remains material, plan inspection or engineering review before the item is put into service.
The output is usually a reconstructed equipment record plus a clear statement of what is known, what is assumed and what must be verified before the receiver can be treated as compliant for its intended use.
Existing receiver with a proposed additional connection
A site wants to add a connection to an existing compressed-air receiver to support an extra take-off point.
The registration question now intersects with alteration control. The issue is not only whether the original receiver needed registration, but whether the proposed change affects the integrity or documentation basis.
What made the job difficult
- The original drawing package is incomplete.
- The new connection may alter local stresses and inspection needs.
- The owner assumes the small size of the nozzle makes the change trivial.
How the review should proceed
- Confirm the vessel identity, class and current service history before treating the change as minor.
- Assess the alteration against the pressure-vessel integrity framework rather than as a simple workshop fitting task.
- Review whether the compliance record, inspection basis or registration record needs update after the change.
- Set testing and examination expectations before the shutdown work starts.
The answer shifts from a simple registration question to a broader integrity and change-control process. Even a modest alteration can trigger the need for a more formal engineering basis.
Information to gather before deciding
Nameplate data and serial identification
Internal volume or dimensions that allow volume calculation
Maximum allowable/design pressure and service conditions
Design code, manufacturer documentation and drawings if available
Inspection, repair and alteration history
Jurisdiction and site compliance requirements