ph-iata-dangerous-goods-air common mistakes
ph-iata-dangerous-goods-air · Understand the traps and how to avoid them.
Treating the IATA DGR as the sole legal authority and applying its rules without checking whether the State of Origin, Transshipment, or Destination has filed a variation or whether the operator has filed a stricter variation that overrides the DGR default.
Candidates learn the DGR in isolation and mentally model it as a single global rulebook. The DGR is contractual/industry text that only becomes binding through State regulations and operator acceptance, so the default is a floor, not a ceiling. Candidates also confuse State variations (prefix 'USG', 'FRG', etc.) with operator variations (prefix 'XX-01') and assume all variations are advisory.
What to do instead
For every scenario question, run a three-step check: (1) identify the States involved and any State variation by two-letter prefix; (2) identify the operator and any operator variation by airline code; (3) apply the most restrictive applicable requirement. Drill by writing out, for a sample shipment, the State variations and one operator variation you would need to consult before acceptance.
Assigning a UN number and proper shipping name by matching the substance's common name to the alphabetical index and stopping there, without cross-checking the Dangerous Goods List entry for the correct packing group, subsidiary risk, or the possibility that the index entry points to a generic 'n.o.s.' or 'not otherwise specified' name requiring technical-name supplementation.
The index is fast and feels authoritative, so candidates treat a hit as the answer. Many substances appear under multiple entries with different packing groups, and some index entries explicitly redirect to a generic entry. Candidates also forget that a 'n.o.s.' entry must be supplemented with the correct technical name in parentheses on the Shipper's Declaration and in marking.
What to do instead
After any index hit, always open the numbered DGL entry and verify: UN number, exact PSN, class/division, subsidiary risks, PG, labels, packing instruction, and special provisions. If the entry is n.o.s., select the correct technical name from the class-specific list and confirm it is not a name already listed elsewhere. Practise with substances that have multiple plausible entries.
Classifying a substance by its commercial name or safety-data-sheet headline rather than by its physical/chemical properties and the class definitions and precedence rules, and failing to apply the hierarchy when a substance meets criteria for more than one class.
Candidates default to the SDS 'transport' section or the product label, which may be generic, outdated, or use a different regulatory framework. They also do not internalise that some classes take precedence (e.g., certain Class 1 and Class 7 considerations, or the treatment of articles containing multiple hazards) and that subsidiary risk does not change the primary class.
What to do instead
Classify from first principles using the class definitions and test criteria: flash point and boiling point for Class 3, the full Class 8 assignment logic, the Class 9 miscellaneous criteria including environmentally hazardous and elevated-temperature provisions. Then compare with the DGL. Where a substance meets multiple criteria, apply the precedence rules explicitly and record the reasoning on the declaration.
Selecting a packing instruction by UN number alone and ignoring the packing group column, the 'Y' or 'X' packaging performance-level letter, the quantity limits per package, and the special packing provisions (e.g., PP, RR, or 'only by passenger/only by cargo aircraft' restrictions) that attach to the entry.
Candidates memorise 'UN XXXX uses packing instruction YYY' as a fact rather than reading the row. They also conflate the packing instruction number with the packaging performance mark, and they miss that the same UN number can have different packing instructions for passenger versus cargo aircraft.
What to do instead
Always read the full DGL row and the packing instruction columns for both passenger and cargo aircraft. Then open the packing instruction and confirm: permitted packaging types, PG performance level, maximum net quantity per package, and any special packing provisions. Verify the packaging's UN mark decodes to the correct code letter, PG, and gross mass.
Marking and labelling the package from memory or from the DGL entry only, omitting one of: the UN number and PSN, the shipper/consignee identification, the net quantity, the correct hazard label(s) including subsidiary risk labels, the orientation labels for combination packagings containing liquids, the 'Cargo Aircraft Only' label, or the overpack marking requirements.
Marking and labelling is treated as a cosmetic final step rather than a compliance step, and candidates under-rehearse the full checklist. Subsidiary risk labels are frequently dropped because the candidate reads only the primary class. Overpacks are commonly missed because the candidate thinks in terms of the inner package.
What to do instead
Use a fixed marking/labelling checklist for every practice item: UN number and PSN, full name and address of shipper and consignee, net quantity (where required), hazard label(s) for primary and subsidiary risks, orientation arrows for liquid combination packagings, Cargo Aircraft Only label where applicable, and for overpacks the 'Overpack' marking plus reproduction of all marks and labels. Recite the checklist aloud before answering.
Completing the Shipper's Declaration with the wrong sequence or missing fields, for example omitting the 'Aircraft Limitations' or 'Radioactive' boxes, putting the packing group in the wrong column, failing to add the technical name for n.o.s. entries, or signing without the required certification statement wording.
Candidates treat the declaration as a form to fill rather than a legal certification. The column order (UN number, PSN, class/division, subsidiary risk, PG, quantity, packing instruction) is easy to scramble, and the certification wording is often paraphrased instead of quoted. Candidates also forget that the declaration is only valid with the correct number of copies and the correct signature authority.
What to do instead
Rehearse the declaration field-by-field in the required order and write out the certification statement verbatim. Check the 'Aircraft Limitations' box (passenger/cargo) and the 'Radioactive' box explicitly. For n.o.s. entries, confirm the technical name appears in parentheses after the PSN. Verify the signatory is authorised and that the declaration accompanies the shipment with the correct number of copies.
Assuming dangerous goods can be loaded anywhere in the aircraft and next to anything else, ignoring the loading, stowage, and segregation requirements: keeping packages away from crew and passenger areas, segregating incompatible classes, securing packages against movement, and applying the correct loading restrictions for cargo aircraft only.
Candidates think of loading as a warehouse task, not a regulatory one, and they do not connect the DGL's aircraft limitation to the physical stowage plan. Segregation tables and the rules on stowage away from living quarters and heat sources are under-rehearsed, and the difference between 'cargo aircraft only' and 'passenger and cargo aircraft' is often reduced to a label rather than a loading decision.
What to do instead
For each scenario, state the aircraft limitation from the DGL, then the stowage location (accessible vs inaccessible, away from crew/passenger areas, away from heat/ignition sources), then the segregation from incompatible goods, then the securing method. Practise with mixed loads and identify which pairs must be separated and why.
Handling an emergency-response or incident-reporting question by giving generic first-aid or firefighting advice instead of using the Emergency Response Drill Codes (ERD) and the associated guide, and failing to state the notification and reporting chain and timelines for a dangerous goods incident.
Candidates rely on general safety knowledge and do not learn that the DGR assigns an ERD code to each entry, which drives the response actions. Incident reporting is often reduced to 'tell the captain', missing the operator's reporting obligation, the State notification, and the requirement to preserve evidence and complete the occurrence report.
What to do instead
For each entry, look up the ERD code and read the corresponding drill. For incidents, rehearse the chain: immediate response and crew notification, notification to the operator's DG office, notification to the State of Occurrence and the State of the Operator as required, and completion of the dangerous goods occurrence report with the correct timeline. State the code and the specific actions, not generic advice.
Performing an acceptance check by spot-checking one or two items (e.g., looking at the label) rather than running the full acceptance checklist: documentation completeness and accuracy, package condition and marking/labelling, quantity limits, compatibility of the declared entry with the packaging, and the aircraft limitation.
Candidates under time pressure default to the most visible cue. They also do not know that the acceptance check is a defined sequence with a hold point: if any item fails, the shipment is rejected and the discrepancy recorded, not 'fixed' by the acceptance agent.
What to do instead
Work through the acceptance checklist in a fixed order: declaration completeness and signature, DGL verification, packaging and quantity, marking and labelling, package condition, aircraft limitation, and operator/State variations. Practise rejecting shipments and writing the discrepancy note. State explicitly that the agent must not alter the shipment or the declaration.
Treating training as a one-off certificate and answering competency questions by reciting the regulation rather than demonstrating the function-specific knowledge and the recurrent/competency-based assessment requirements, including the need to reassess after regulatory change.
Candidates conflate 'having attended a course' with 'being competent' and do not distinguish the categories of personnel requiring training (shippers, packers, forwarders, operators, ground handlers, acceptance staff, crew). They also miss that competency-based assessment requires evidence of applied performance, not just a written test, and that recurrent training intervals and reassessment triggers are specified.
What to do instead
Learn the personnel categories and the function-specific content each must know, then the assessment requirements: initial and recurrent intervals, competency-based verification of applied tasks, record retention, and reassessment after significant regulatory change. For scenario questions, identify the person's function first, then the training and assessment obligation that attaches to that function.