Airspace coordination in HADR

Separate roles before planning

Scope as of 15 October 2026: a public-review lesson without documented aviation-expert endorsement. It supports tabletop learning, not flight authorization or a pre-flight briefing. This research did not cover a complete live NOTAM set. Before real operations, check date, time, area, aircraft and mission conditions through the responsible channels.

ICAO HADRA addresses preparedness across aviation and humanitarian actors, airport–ATC coordination and onward movement of relief cargo. This connects aviation requests to the people receiving assistance.

Original project role map: requesters state needs, coordinators consolidate questions, operators assess readiness, aviation roles address conditions/authority within their remit, and information staff prepare products. The label ‘coordinator’ does not establish clearance authority. In Thailand, check CAAT, NBTC, AEROTHAI and responsible-area roles separately against the sources below. Military/civilian roles in the exercise are fictional, not a new real command structure.

Registration and authorization are different questions

NBTC’s FAQ distinguishes possessor registration with NBTC from remote-pilot registration with CAAT. CAAT No. 16, signed 25 June 2026 and effective 26 June until changed, repeals No. 15 and provides a conditional pathway for disaster-relief requests in covered areas. Clause 10’s listed state-service provision is tied to statutory duties, not every volunteer or HADR mission.

The Ministry of Transport’s 2015 notice sets ordinary conditions in clauses 5, 9 and 13 and a different-conditions permission route in clause 17. Aircraft over 25 kg require checking the 2024 framework, whose clause 3 repeals old 2015 clause 18, with 2025 amendment No. 2 and 2026 No. 3 replacing clause 23/1. Heavy-drone delivery therefore cannot automatically rely on another weight category’s rules. This is an educational source map, not a consolidated flight manual or qualification determination.

For operations differing from prescribed conditions under CAAT’s 2026 notice covering aircraft up to 25 kg, consult clauses 3–5 on risk assessment and prior permission, alongside amendment No. 2 dated 23 June 2026. This lesson does not summarize all training requirements or extend that instrument to every aircraft category.

Original record: use separate fields for registration/operator evidence, mission permission, area restrictions and coordination. Mark each ‘confirmed/pending/conflicting’ with source, time and follow-up owner. Never fill a gap with ‘an emergency makes it permitted’ or equate submission with approval.

Read time and scope in aeronautical information

HADRA distinguishes AIP’s lasting aeronautical information from time-sensitive NOTAM changes and hazards. AEROTHAI describes its Bangkok FIR International NOTAM Office and AIS/ARO pre-flight information services. Knowing a website gateway is not a complete mission briefing.

Checked example: CAAT’s VT R1 Bangkok City notice, signed 12 October 2026, specifies 16 October 2026, 00:01–23:59 Thailand time for its flight prohibition. Clause 2 provides limited meeting-related necessary-flight exceptions requiring prior permission. Signature date differs from the flight window. At the 15 October research cutoff, that window is the following day, not a permanent or conference-wide prohibition.

Project reading method: record notice identity, issuer, signature date, flight-validity window, time zone, area, amendments/cancellations and questions for competent interpretation. An inaccessible document means ‘unchecked’, not ‘unrestricted’. The CAAT AIP index checked on 15 October listed AIRAC AIP AMDT 10/26 effective 1 October 2026. This index check is not a mission-route/area review or complete NOTAM briefing. Times outside the example are not declared clear to fly.

UTM and a shared picture that is not clearance

The inspected ICAO UTM webpage labels its overview Edition 3. It discusses sharing flight intentions and constraints, interaction with ATM and UAS operator responsibility within conditions. An Edition 4 menu link failed to retrieve. No Edition 4 detail or nationwide Thai implementation is claimed.

The original exercise applies this as a request board, not a certified UTM system: record mission ID, need, fictional area/time, operator, verification status, question recipient, information version and acknowledgement. A coordinator may record a medical urgency request but does not decide clinical suitability or invent aircraft separation. When requests overlap, relay necessary information to the aviation role and retain the card’s status until answered.

Connect D05 and D10: in the fictional task, a patient-transfer request needs a medical receiving role and cargo needs an onward ground recipient. Identify missing information and consequences for people awaiting assistance. Explain request priorities from the cards rather than agency prestige or pressure.

Fictional CPX: three competing requests

Entirely original exercise: ‘Khlong Ruam Chai’ uses paper areas A/B/C without real coordinates, altitude, radio frequency or separation. Roles are a civilian HADR coordinator, fictional military liaison, drone operator, medical team, logistics team, aviation role and exercise control. Control provides fictional learning responses only, never real CAAT/ATC authority.

Card A — T+0 / request desk: ‘D1 requests route imagery over A; registration is on file but mission permission is blank. H1 requests helicopter patient transfer from clinic C through A; timing and the destination receiving team are unconfirmed. L1 requests cargo at B; onward ground transport has not replied. Coordinators may consolidate requests but cannot authorize flight.’ Task: create three board entries separating known facts, gaps, evidence of urgency and question recipients. Invent no times or routes.

Card B — T+10 / update: ‘Exercise restriction R2 replaces R1: new requests in A remain pending aviation-role review until answered. H1 changes its requested window, still unconfirmed. D1 already sent an R1 screenshot to volunteers. A community representative flags a patient name on the public board.’ R1/R2 are fictional card labels, not real NOTAMs. Task: compare versions, correct prior recipients, identify required acknowledgements and reduce patient data on the public board.

Card C — T+20 / handover: ‘The aviation role has not answered D1. Medical staff confirm H1’s receiving team but no flight confirmation exists. L1 has onward transport, but the warehouse requests a new recipient. The coordinator must leave and one volunteer still holds R1.’ Task: hand over each request, distinguish one resolved dependency from complete approval, ask the receiver to restate gaps/owners and issue a revised board with change history.

Log reasons and check shared understanding

Original required record: a one-page role map, D1/H1/L1 board and per-change log. Fields are exercise time, card/version, new information, action, rationale, authorization status, owner, notified recipients/acknowledgements and next checks. Add one real-source reading entry for the VT R1 example, separating signature date from flight window and noting that it is not complete geographic coverage.

Facilitator interpretation: A leaves incomplete requests pending. B corrects people already holding R1 and removes patient details from the public version with a recorded rationale. C does not turn ‘receiver confirmed’ into ‘flight confirmed’. If the incoming coordinator restates a status incorrectly, repair the communication and log it. Ask who may be affected by delay and what alternatives can be referred to responsible roles. Never solve delay by inventing clearance.

Debrief without overclaiming competence

HADRA supports collaborative review and exercises addressing service/infrastructure disruptions. Original project debrief questions are: which information changed a decision, who missed a correction, who owns unresolved questions, and what explanation aligned understanding? Compare work before and after injects rather than scoring speed or confidence alone.

Assess one rubric criterion per KSEC domain, citing behaviour across at least two rounds and inviting learners to identify their evidence. Five quiz items check K and parts of reasoning. S requires the board and handover; E/C need explanations and repeated behaviour within the exercise. These results do not certify air traffic controllers, remote pilots, real decision authority or lasting character.