Floating Roof Per API 650 Appendix H (External)
Created on Today
Floating Roof Per API 650 Appendix H (External)
External floating-roof design rules for open-top tanks. The requirement is met by following its design criteria and linking them to floating-roof type, seal class and inspection - not by a generic statement of conformance.
Scope And Application
External floating-roof design rules for open-top tanks. It applies where the tank duty falls inside its boundary; outside that boundary a different standard governs and must be identified before design. Quoting a standard number without checking scope is a frequent non-conformance.
Key Requirements
· Deck type selection (pontoon, double-deck)
· Rim seal and wind girder interaction
· Shell out-of-roundness tolerance
· Rain and snow load paths
Key Clauses (Illustrative)
The specific clause topics that most often drive floating-roof design are listed below. They are illustrative of the subjects the standard addresses; the exact clause numbers belong to the current edition and must be read from the source document rather than paraphrased from this summary.
· Deck type decision (pontoon vs double-deck)
· Rim seal class and wind-girder interaction
· Shell out-of-roundness acceptance
· Rain and snow live-load path
How It Maps To Floating-Roof Selection
The standard sets the envelope; the floating-roof type, deck and seal are then selected inside it. Skipping the mapping produces a tank that is 'referenced' but not actually compliant. The chain is: duty -> standard -> roof type -> seal class -> inspection.
Selection And Design Method
A repeatable method keeps the choice defensible across similar tanks:
1. Confirm the tank duty falls inside the scope of API 650 APPENDIX H.
2. Extract the binding criteria (e.g. Deck type selection (pontoon, double-deck)).
3. Select the floating-roof type inside those criteria.
4. Document the compliance path for audit.
5. Set the inspection basis from the API 650 APPENDIX H family.
Requirement Table
Requirement | Control | Verification |
Requirement | What it controls | Verification |
Scope | Which tanks apply | Duty check |
Design criteria | Deck type selection (pontoon, double-deck) | Calculation / drawing |
Compliance link | Rain and snow load paths | Inspection record |
Illustrative Parameter Ranges
The table shows the typical parameters the standard governs. The values are illustrative of the kind of limit involved; the actual numerical limit comes from the applicable edition and the project specification, and must not be quoted as a measured figure for any named tank.
Parameter (illustrative) | Typical basis | Why it matters |
Deck type | Pontoon or double-deck | Driven by buoyancy and load |
Wind girder | Per Appendix D | Controls shell stability |
Shell roundness | Within tolerance | Keeps the seal in contact |
Live load | Rain + snow | Sized into the deck |
Compliance Documentation Checklist
Document | Proves |
Document | What it proves |
Design calculation | The criteria are met numerically |
General arrangement drawing | Geometry matches the standard |
Material certificate | Grade per the specification |
Inspection record | Condition assessed per API 650 APPENDIX H / API 653 where applicable |
Verification By A Qualified Engineer
The standard is a reference, not a self-executing control. A qualified engineer confirms that the tank duty falls inside the scope of API 650 APPENDIX H, that the design criteria are met numerically, and that the inspection basis is set. Where a jurisdiction or contract requires it, a certified inspector records the condition per the relevant program. This step is what converts a cited number into documented conformance; without it the tank may appear compliant on paper while drifting from the code envelope in service.
Common Non-Compliance
· A tank cited to API 650 APPENDIX H but with duty outside its scope.
· Deck type selection (pontoon, double-deck) not carried into the calculation or drawing.
· Rain and snow load paths left as a statement rather than an inspection record.
Clause-To-Action Checklist
Clause | Action |
Standard clause | Action in practice |
Scope | Confirm duty is inside scope before design |
Design criteria | Deck type selection (pontoon, double-deck) |
Compliance link | Rain and snow load paths |
Interaction | Map to roof, seal and venting |
Interaction With Other Standards
API 650 APPENDIX H does not stand alone: it interacts with API 650 for the shell, API 2000 for venting, API 653 for inspection and the relevant emissions or fire code. A tank is compliant only when the chain is closed, not when one document is cited.
Typical Design Workflow
A practical workflow keeps the API 650 APPENDIX H chain closed: (1) confirm the duty is inside scope, (2) extract the binding criteria of API 650 APPENDIX H, (3) size the roof, deck and seal inside them, (4) document the compliance path, and (5) set the inspection interval. Skipping any step leaves a gap that later appears as vapor loss, corrosion or a failed audit.
Common Specification Mistakes
· Citing API 650 APPENDIX H without checking its scope.
· Treating conformance as a statement rather than a record.
· Ignoring the inspection and maintenance link.
· Letting roof and seal drift from the API 650 APPENDIX H envelope.
Engineering Support And Next Steps
For API 650 APPENDIX H, share the product name and concentration, operating temperature, vapor pressure, the design code, tank diameter, volume and turnover. An engineer then confirms the roof type for API 650 APPENDIX H, the deck and seal class and the inspection basis rather than a one-size recommendation.
Frequently Asked Questions
1. What does Floating Roof Per API 650 Appendix H (External) cover?
External floating-roof design rules for open-top tanks.
2. Is it mandatory?
Applicability follows the project's jurisdiction and contract; the standard is cited as the engineering basis, not as a universal legal mandate.
3. How does it affect roof type?
It bounds deck, seal and tolerance choices; the roof is selected inside those bounds.
4. What is verified?
Design calculations, drawings and inspection records confirm conformance.
5. What happens if ignored?
The tank may pass a paperwork check but fail in service - vapor loss, corrosion or seal fire.
6. Who confirms compliance?
For API 650 APPENDIX H, a qualified engineer and - where required - a certified inspector per the program confirm conformance.
7. Can I claim conformance without records?
No - for API 650 APPENDIX H the proof is the documented calculation and inspection record, never just a statement.
Floating Roof Per API 650 Appendix H (External) is decided by the specific stored product, its vapor pressure, temperature, corrosion environment and the applicable code - not by habit. Start from the service conditions, map them to the correct floating-roof type and seal class, then verify the deck, seal and shell tolerances against the chosen standard. Where project-specific dimensions, tank quantity or capacity are required, confirm them against the verified tank record before finalising the specification.
WhatsApp