PUBLIC SPECIMEN -- Mission FOM generated from OM Appendix 5 ·
flightdocket.com
Fictional mission data. Not an authorisation. FlightDocket recommends; the tenant approves; the PIC opens the mission.
MISSION FIELD OPERATIONS MANUAL
Generated from OM Appendix 5 -- Field Operations Manual (OM-A5)
0.1 WORKFLOW STATES
The four workflow events below are produced by separate actors at separate timestamps. No single banner authorises this mission. The PIC remains responsible for final on-site release.
STATE 1 / 4
System Recommendation
recommendation_complete
FlightDocket Operate (auto)
2026-05-08T05:30:00+02:00
Inputs validated. Mission within scope.
STATE 2 / 4
Tenant Mission Approval
tenant_approved_for_pic_review
Approver: M. Raath (Mission Approver)
actor_id redacted
2026-05-08T05:42:11+02:00
STATE 3 / 4
FOM Sync to PIC Device
synced_to_pic
PIC device id redacted
2026-05-08T05:48:03+02:00
FOM v1 hash matches.
STATE 4 / 4
PIC Mission Open
awaiting_pic_open
PIC: J.A. Raath (Remote Pilot)
Declaration block at end of FOM.
Flight may not commence until PIC opens.
Authority and roles. FlightDocket is an authoring, evidence, and operational-governance platform. It does not authorise flight. The tenant remains the accountable operator. The tenant mission approver grants internal mission approval. After approval, the FOM is distributed to the PIC and crew devices. The PIC remains responsible for final on-site review, current-condition verification, checklist completion, and formal mission opening before flight commencement.
FlightDocket System Recommendation: RECOMMEND PROCEED -- subject to gates closed
Specimen value. Recommendation is advisory only and does not authorise flight.
1. PURPOSE AND STATUS
This Mission FOM is the populated operational instance of OM Appendix 5 -- Field Operations Manual. It is a quick-reference document carried on site for this specific mission. All Appendix 5 mandatory content blocks (contact numbers, airspace, weather, permissions, documentation on site) are present and complete; system-derived content (maps, C2, flyaway, hazards, radio scripts, pre-flight checklist, IMSAFE, sign-off, provenance) follows the Appendix 5 core.
| Operator (Tenant) | Southwest Unmanned Aerial Systems (Pty) Ltd (specimen) |
| Operator UASOC | scope-bound Reference UASOC-SPEC-XXX -- active. Specimen reference; no operational authority. |
| Operator OpSpec | verified OpSpec line items: VLOS, EVLOS, BVLOS-001 (corridor), Night-NIL. |
| Document Authority | This FOM is produced by FlightDocket and authorised internally by the tenant mission approver. It is not an SACAA-issued authorisation. Flight authority is the tenant's UASOC and OpSpec; FlightDocket records that they were verified at generation time. |
2. MISSION SUMMARY
| Mission Type | Linear infrastructure inspection -- rail corridor |
| Operating Mode | BVLOS -- corridor profile; observers at three relay points |
| Planned Date | 2026-05-08 (Friday) -- 06:00 to 12:00 SAST |
| Pilot in Command | J.A. Raath, RPL-A-XXXX, Class 3 medical valid 2026-12-31 (specimen) |
| Crew | Observer 1: M. Raath (RPL-A-YYYY); Observer 2: spotter; Ground crew: 2 |
| Operating Area Centre | Kathu rail corridor -- coordinates redacted in specimen |
| Operating Area Size | 16.4 km corridor × 200 m buffer |
| Max Altitude AGL | 120 m AGL (within 121 m / 400 ft Part 101 ceiling) |
| Max Operating Radius from Home | 6.4 km (BVLOS corridor relays) |
| Mission Model | Single mission, no repetition. Not part of a recurring pattern. |
2.1 Canonical Aircraft Snapshot
The values below are the single canonical aircraft snapshot for this mission. If any field on this row had been inconsistent between systems, the FOM would not have rendered.
| Aircraft Model | DJI Matrice 350 RTK |
| Registration | ZS-RPA-0042 (specimen registration; not allocated) |
| MTOM | 9.2 kg (Class 1B per CARs Part 101 mass classification) |
| Max Airspeed | 23 m/s (82.8 km/h) |
| Max Endurance (with payload) | 42 minutes |
| Worst-Case Flyaway Radius | 57.96 km (endurance × max airspeed) |
| C2 Primary | DJI OcuSync 3 Enterprise -- 2.4 / 5.8 GHz ISM, dual-band |
| C2 Backup | 4G LTE failsafe (range > 30 km, source: cellular RSRP ≥ -110 dBm at relay 2) |
| Lost-Link Action | Return to Home (RTH); RTH altitude 130 m AGL; loiter 60 s |
| Geofence Action | RTH on breach |
| AMP Status | released to service AMP-Rev-04, last cycle 2026-05-01, next due 2026-08-01 (50 flight hours) |
| OpSpec Reference | OpSpec line BVLOS-001 (corridor profile, ≤ 10 km, ≤ 120 m AGL, observers required) |
3. EMERGENCY AND OPERATIONAL CONTACT NUMBERS
Categories are in OM Appendix 5 order. Each row carries source, last-verified timestamp, status, and dispatch effect. Any contact category marked not_available blocks tenant approval; none survive in this FOM.
| Category | Name | Phone | Source | Last Verified | Status | Dispatch Effect |
| Client / Landowner | Transnet Freight Rail (Sishen line) (specimen) | +27 53 723 XXXX | Tenant contact register | 2026-05-07 | verified | Pre-flight notification call required |
| Local Aerodrome (CTAF) | FASS -- Sishen Airport (CTAF 123.500 MHz) | +27 53 723 7000 | SACAA AIP / Aerodrome directory | 2026-05-07 | verified | CTAF advisory before launch and before recovery |
| Manned-aircraft Operator | Sishen-based mining helicopter ops -- Anglo American Aviation | +27 53 723 XXXX | Operator coordination register | 2026-05-06 | verified | Notify before BVLOS leg |
| Police | SAPS Kathu | 10111 / +27 53 723 6000 | SAPS station directory | 2026-05-07 | verified | Incident escalation |
| Fire | Gamagara Local Municipality Fire Services | +27 53 723 XXXX | Municipal directory | 2026-05-07 | verified | Incident escalation |
| Nearest Hospital | Kathu Private Hospital (Lenmed) | +27 53 723 XXXX | Hospital directory | 2026-05-07 | verified | Casualty referral |
| Operator Management | Accountable Manager -- J.A. Raath | +27 82 XXX XXXX | Tenant management register | 2026-05-08 | verified | Internal escalation |
| Operator Management | Safety Manager -- M. Raath | +27 82 XXX XXXX | Tenant management register | 2026-05-08 | verified | Safety escalation |
| SACAA Occurrence Reporting | SACAA Aviation Safety Investigation | +27 11 545 1000 / occurrence@caa.co.za | SACAA published contacts | 2026-05-01 | verified | Mandatory occurrence report channel |
| ICASA / RF route | ICASA Type Approval / Spectrum -- required only if RF interference suspected | +27 11 566 3000 | ICASA published contacts | 2026-05-01 | verified | RF incident channel |
Source: OM Appendix 5 §3. Specimen phone numbers shown as redacted XXXX.
4. AIRSPACE
4.1 Primary Classification
| Airspace Class | Class G (Uncontrolled) |
| ATC Clearance Required | No (Class G) |
| ATC Coordination Required | YES -- aerodrome-proximity rules apply in addition to airspace class |
Aerodrome-proximity advisory. The home point is 0.1 km north of FASS -- Sishen Airport (CTAF 123.500 MHz). Aerodrome-proximity rules apply in addition to airspace-class rules. ATSU/CTAF coordination is required regardless of airspace class.
• Coordination route: Sishen CTAF 123.500 MHz, advisory call before each launch and before each recovery.
• OpSpec condition: BVLOS-001 corridor profile permitted only with CTAF advisory and visual observer chain.
• Permission requirement: aerodrome operator notified per OM Appendix 5 §6.
4.2 Controlled Airspace Within Reach
| Name | Class | Distance | Bearing | Vertical Limits | Coordination |
| FASS Sishen -- Aerodrome Traffic Pattern | Class G + CTAF | 0.1 km | N (002°) | SFC -- AAL+1500 ft | CTAF 123.500 MHz advisory |
| FAUP -- Upington CTR (next controlled airspace) | Class D / E | ~310 km | SW | SFC -- UNL | Not affected by mission |
4.3 Restricted / Danger / Prohibited Areas
| Designator | Name | Distance | Bearing | Vertical Limits | Effect |
| FAR25 | Ga-Tlhose / Maremane Military Shooting Range | 42.1 km | SE (131°) | SFC -- FL195 | Outside operating area -- no entry planned |
| FAR23 | Botterduim Military Shooting Range | 147.9 km | W (266°) | SFC -- FL195 | Outside reach |
4.4 NOTAMs (FIR FACT, FAJA -- relevant)
| Source | Reference | Coverage | Effect on Mission | Last Verified |
| ATNS File2Fly | FACT NOTAM A1234/26 (specimen) | FACT FIR -- UAS activity advisory | None -- outside operating area | 2026-05-08T04:55:00+02:00 |
| ATNS File2Fly | FAJA NOTAM B0567/26 (specimen) | FAJA FIR -- standard cautions | None | 2026-05-08T04:55:00+02:00 |
Source: ATNS File2Fly. SAWS / ATNS / File2Fly status table in §6 below. Foreign (non-FACT/FAJA) SIGMET products are filtered at source.
5. WEATHER
| Flight Category | VFR |
| Wind | within limits 360° / 06 kt -- below 10 m/s threshold (ENV-001) |
| Visibility | within limits 10 km+ |
| Ceiling | within limits FEW040 |
| Precipitation | caution TEMPO TSRA -- see TAF |
| METAR (FASS) | FASS 080500Z 36006KT 9999 FEW040 18/06 Q1019 |
| TAF (FASS) | TAF FASS 080430Z 0806/0820 36008KT 9999 SCT040 TEMPO 0812/0816 TSRA BKN030CB |
5.1 SIGMETs / AIRMETs (FACT, FAJA only)
| FIR | Type | Hazard | Severity | Excerpt |
| FACT | No active SIGMET / AIRMET in FACT FIR at retrieval time. |
| FAJA | No active SIGMET / AIRMET in FAJA FIR at retrieval time. |
5.2 South African Weather / NOTAM Source Status
| Source | Type | Status | Retrieved At | Gate Effect |
| SAWS Aviation METAR/TAF | METAR/TAF | OK | 2026-05-08T05:25:00+02:00 | Pass |
| ATNS File2Fly NOTAM | NOTAM | OK | 2026-05-08T04:55:00+02:00 | Pass |
| ATNS SIGMET / AIRMET (FACT, FAJA) | SIGMET/AIRMET | OK | 2026-05-08T05:25:00+02:00 | Pass |
| SANSA Space Weather (Kp Index) | Space weather | OK | 2026-05-08T05:00:00+02:00 | Pass -- Kp 2 (quiet) |
Source-integrity advisory. Only mission-relevant South African weather, NOTAM, SIGMET/AIRMET, FIR, SAWS/ATNS/File2Fly products are accepted. Foreign products (e.g. WSUS-prefixed convective SIGMETs) are filtered at source. If any SA source is unavailable, tenant approval and PIC mission-opening are blocked until verified.
CAR Part 101 §101.05.8 -- Weather assessment required before flight. SACAA TGM Part 101 §6.3 -- operational weather sources.
6. PERMISSIONS
Each permission row carries status, evidence ID, validity window, and dispatch effect. Missing or expired permissions block tenant approval.
| Permission | Status | Evidence ID | Valid From | Valid Until | Dispatch Effect |
| Landowner / land-access permission | verified | EVD-LAND-2026-018 | 2026-05-01 | 2026-12-31 | Pass |
| FUA (Flexible Use of Airspace, where applicable) | not applicable | -- | -- | -- | Class G; no FUA call-up needed |
| ATSU coordination (CTAF advisory) | verified | EVD-ATSU-2026-007 | 2026-05-08 | 2026-05-08 | CTAF 123.500 advisory required at launch and recovery |
| FAR / FAP authority (military / restricted / FAP airspace) | not applicable | -- | -- | -- | No FAR/FAP intersection |
| Strategic installation / NKP / police / court | not applicable | -- | -- | -- | No strategic installation in operating area |
| Municipal / Disaster Management Centre | verified | EVD-DMC-2026-003 | 2026-05-01 | 2026-05-31 | Pass -- Gamagara DMC notified |
| CA 101-18 (BVLOS / non-standard ops application) | verified | EVD-CA10118-2025-091 | 2025-09-15 | 2026-09-14 | BVLOS corridor profile authorised under OpSpec BVLOS-001 |
| CA 101-20 (waiver / deviation, where applicable) | not applicable | -- | -- | -- | No deviation requested |
7. DOCUMENTATION ON SITE
OM Appendix 5 minimum set, augmented with carrier, evidence ID, synced-to-device status, PIC acknowledgement, and last-verified timestamp.
| Document | Carrier | Evidence ID | Synced to PIC Device | Last Verified | PIC Ack |
| Landowner / land-access permission | PDF on tablet + paper | EVD-LAND-2026-018 | synced | 2026-05-08T05:48:00+02:00 | [ ] |
| Operating area map | PDF + Mission FOM §8 | EVD-MAP-2026-018 | synced | 2026-05-08T05:48:00+02:00 | [ ] |
| UASOC / OpSpec | PDF on tablet | UASOC-SPEC-XXX / OPSPEC-2025-04 | synced | 2026-05-01 | [ ] |
| RLA / UASLA (if applicable) | -- | -- | not applicable | -- | -- |
| Aircraft user / flight manual | PDF on tablet | EVD-MAN-M350-RTK | synced | 2026-04-15 | [ ] |
| Certificate of Registration (ZS-RPA-0042) | PDF on tablet | EVD-COR-ZS-RPA-0042 | synced | 2026-04-01 | [ ] |
| Insurance certificate (third-party + hull) | PDF on tablet | EVD-INS-2026-Q2 | synced | 2026-04-01 | [ ] |
| Remote Pilot Licence (RPL) -- PIC | PDF on tablet | EVD-RPL-JAR | synced | 2025-12-15 | [ ] |
| Flight Folio (current) | App + PDF | EVD-FF-2026-0142 | synced | 2026-05-08T05:30:00+02:00 | [ ] |
| Operations Manual (OM) | PDF on tablet | EVD-OM-Rev-04 | synced | 2026-04-15 | [ ] |
| Mission risk assessment | Mission FOM §10 | EVD-RA-MSN-001 | synced | 2026-05-08T05:30:00+02:00 | [ ] |
| NOTAMs (FACT, FAJA) | Mission FOM §4.4 | EVD-NOTAM-2026-05-08 | synced | 2026-05-08T04:55:00+02:00 | [ ] |
8. OPERATIONAL AREA MAP
Operational polygon (blue), safety geofence (red), home point (green), nearest aerodrome (FASS), and emergency landing sites. Specimen coordinates redacted to centre-only.
9. C2 LINK AND PROPAGATION
Specimen note. The polygons, link budget, and obstructions in this section are produced by the FlightDocket RF propagation engine. At calculation time the engine evaluates every variable relevant to the link that is present in the mission data pack — by default up to 24 distinct equipment, geometry and propagation-policy parameters per link (TX power, antenna gain, RX sensitivity, cable loss, polarisation and antenna height for the ground and air sides; link frequency; GCS coordinates and AMSL elevation; flight altitude AGL; radial count and sample density; Fresnel-clearance fraction; atmospheric absorption coefficient; fade margin; polarisation-mismatch loss; LoS / NLoS path-loss exponents; LoS / NLoS shadowing margins; outage percentile) — together with SRTM elevation samples along N radials. The coverage pattern is projected as accurately as the available mission data permits and is not a set of nominal/max OEM circles. The specimen below shows the structure with fictional but Friis-consistent numbers.
Inner solid polygon = LoS-guaranteed coverage (link budget − σLoS margin, terrain blockage applied). Outer dashed polygon = NLoS-extended coverage (with NLoS path-loss exponent αNLoS + σNLoS). Faint dashed circle = free-space FSPL upper bound (no terrain). Red dots = terrain obstruction points along sample radials.
9.1 Link Budget (Friis FSPL -- specimen, OcuSync 3 class)
| Parameter | Value | Source |
| Link | C2 Primary -- 2400 MHz uplink (GCS → aircraft) | Mission C2 link record |
| GCS TX power | 30.0 dBm | GCS equipment record (specimen, OcuSync 3 class) |
| GCS antenna gain | 3.0 dBi | GCS equipment record |
| GCS cable loss | 1.0 dB | GCS equipment record |
| EIRP | 32.0 dBm | Derived: TX power + antenna gain − cable loss |
| Aircraft RX sensitivity | −101.0 dBm | Aircraft equipment record |
| Fade margin | 10.0 dB | Operator propagation policy |
| Polarisation mismatch loss | 0.0 dB | Operator propagation policy (matched) |
| RX threshold | −91.0 dBm | rx_sensitivity + fade_margin |
| Max FSPL budget | 123.0 dB | EIRP − rx_threshold |
| FSPL @ 1 km, 2400 MHz | 100.05 dB | Friis: 20·log10(d) + 20·log10(f) − 147.55 |
| Free-space max range (no terrain) | 14.0 km | 10(123 − 100.05) / 20 × 1 km |
| LoS-guaranteed range (terrain + σLoS) | 6.5 km min / 12.0 km max | Per-radial worst/best across §9.2 |
| NLoS-extended range (αNLoS + σNLoS) | 8.5 km min / 15.0 km max | Per-radial worst/best |
| Operating radius vs LoS-guaranteed worst | 6.4 km vs 6.5 km worst-direction min -- tight margin to E/ESE | Mission plan vs propagation |
| Operations Implication | Observers placed on E and ESE sectors (§11). Approach E/ESE only with relay observer comms-confirmed. | Mission plan |
9.2 Per-Radial Range Table (specimen -- 16 bearings)
The engine samples 16 bearings by default (configurable per operator). Each radial walks an SRTM elevation profile, applies Friis FSPL plus Fresnel-zone clearance and earth-curvature offset, and returns LoS-blocked range, LoS-budget range, NLoS-extended range, and an obstruction list. Specimen values below mirror that shape; the asymmetry is illustrative of terrain shadowing east of the GCS.
| Bearing | Sector | LoS range | NLoS range | Obstructions |
| 000° | N | 11.5 km | 13.0 km | -- |
| 022.5° | NNE | 11.0 km | 12.5 km | -- |
| 045° | NE | 9.5 km | 12.0 km | 1 (ridge @ 6.8 km, −22 m clearance) |
| 067.5° | ENE | 8.0 km | 11.0 km | -- |
| 090° | E | 7.5 km | 10.0 km | 1 (knoll @ 6.2 km, −18 m clearance) |
| 112.5° | ESE | 6.5 km | 8.5 km | 1 (escarpment @ 5.5 km, −31 m clearance) |
| 135° | SE | 8.0 km | 11.0 km | -- |
| 157.5° | SSE | 9.0 km | 12.0 km | -- |
| 180° | S | 10.5 km | 13.5 km | -- |
| 202.5° | SSW | 11.0 km | 14.0 km | -- |
| 225° | SW | 11.5 km | 14.5 km | -- |
| 247.5° | WSW | 12.0 km | 15.0 km | -- |
| 270° | W | 12.0 km | 15.0 km | -- |
| 292.5° | WNW | 11.5 km | 14.5 km | -- |
| 315° | NW | 11.0 km | 14.0 km | -- |
| 337.5° | NNW | 11.5 km | 13.5 km | -- |
Inputs: aircraft and GCS equipment records; operator propagation policy (radial count, fade margin, LoS / NLoS exponents, shadowing σ); SRTM terrain elevation along each radial. Outputs: an inner LoS-guaranteed coverage polygon, an outer NLoS-extended coverage polygon, a per-radial range and obstruction list, and the link budget summarised in §9.1.
9.3 C2 System Snapshot (canonical)
| C2 System (primary) | DJI OcuSync 3 Enterprise -- 2400 MHz / 5800 MHz dual-band ISM |
| Backup link | 4G LTE failsafe -- modelled as a separate link with a cellular RSRP threshold; not free-space-modelled. |
| Operating altitude | 120 m AGL |
| GCS antenna height | 1.5 m AGL (handheld) at 1181 m AMSL |
| Lost-link procedure | RTH at 130 m AGL, loiter 60 s, descend, land at home. Verified pre-flight (§11). |
| Range / source evidence | verified tenant flight-log RSSI ≥ −85 dBm at 6.4 km, last 90 d -- FL-LOG-2026-Q2 |
10. HAZARDS / RISK REGISTER
Scoring uses the operator's approved 5×5 SMS matrix (SMS-1). This FOM does not introduce a separate scoring scheme. L = Likelihood (1-5), S = Severity (1-5), Risk = L × S. Levels: Low (<5), Medium (5-9), High (10-14), Extreme (15+). ALARP = As Low As Reasonably Practicable.
| Code | Hazard | Cat | L | S | Risk | Level | ALARP | Controls / Mitigations |
| ENV-001 | Adverse weather -- wind exceedance | environmental | 3 | 4 | 12 | high | ALARP | Pre-flight wind measurement; abort if > 10 m/s; SAWS METAR/TAF check. |
| TP-001 | Moving trains on rail corridor | third_party | 2 | 5 | 10 | high | ALARP | Coordinate with Transnet; pause ops on train approach; observers on relays. |
| ENV-003 | Thunderstorm / convective activity | environmental | 2 | 5 | 10 | high | ALARP | No ops within 30 km of active TS. SIGMET monitoring (FACT, FAJA). |
| TECH-004 | EMF interference from HV / OHL | technical | 3 | 3 | 9 | medium | ALARP | Compass calibration before corridor ops; min 50 m lateral from HV lines. |
| TECH-001 | C2 link loss | technical | 2 | 4 | 8 | medium | ALARP | Dual-band C2 (2.4 / 5.8 GHz) + 4G LTE backup; RTH on link loss; pre-flight C2 test at max planned range. |
| HF-002 | Loss of situational awareness -- BVLOS | human_factors | 2 | 4 | 8 | medium | ALARP | Max 4-hour sortie; mandatory break; full telemetry on GCS at all times; observer relays. |
| OPS-002 | Mid-air collision with manned aircraft | operational | 1 | 5 | 5 | medium | ALARP | CTAF 123.500 monitoring; advisory call before / after; ADS-B In receiver; observer chain. |
| OPS-003 | Ground impact on uninvolved persons | operational | 1 | 5 | 5 | medium | ALARP | Visual area survey before launch; observers maintain ground sterility along corridor. |
| OPS-001 | Flyaway beyond geofence | operational | 1 | 5 | 5 | medium | ALARP | Geofence loaded and verified; RTH on fence breach. |
| TECH-003 | Battery failure | technical | 1 | 4 | 4 | low | ALARP | Battery ≥ 90% at launch; 20% reserve enforced by RTH. |
| TECH-002 | GNSS degradation | technical | 1 | 4 | 4 | low | ALARP | SANSA Kp index check pre-flight; abort if Kp ≥ 5. |
| HF-001 | PIC fatigue / impairment | human_factors | 1 | 4 | 4 | low | ALARP | IMSAFE self-assessment before every flight; crew crosscheck. |
SMS-1 risk matrix (operator-approved, 5×5). FOM scoring is identical to SMS register; no separate FOM scheme.
11. BVLOS / C2 GATE EVIDENCE
This mission is BVLOS. Each item below must be satisfied; absence of any would render the FOM for review only.
| Gate | Status | Evidence ID | Notes |
| OpSpec authority for BVLOS scope | verified | OPSPEC-2025-04 / line BVLOS-001 | Corridor profile, ≤ 10 km, ≤ 120 m AGL, observers required. |
| Aircraft-specific authorisation | verified | EVD-AC-AUTH-ZS-RPA-0042 | DJI Matrice 350 RTK approved on this OpSpec line. |
| C2 system verification (link health) | verified | EVD-C2-2026-05-08 | Pre-flight RSSI test at 6.4 km: -82 dBm, primary; -88 dBm, backup. |
| Lost-link settings verified | verified | EVD-LOSTLINK-2026-05-08 | RTH at 130 m AGL, loiter 60 s, descend, land at home. Tested. |
| Range / source evidence | verified | FL-LOG-2026-Q2 | Tenant flight log: RSSI ≥ -85 dBm at 6.4 km consistently in last 90 d. |
| Backup-link evidence | verified | EVD-BACKUP-LTE-2026-Q2 | 4G LTE RSRP ≥ -110 dBm at relay 2 (verified 2026-05-07). |
| DAA / observer / airspace mitigation | verified | EVD-OBS-2026-05-08 | 3 observers; CTAF advisory; ADS-B In; corridor sterility plan filed. |
11.1 Worst-Case Flyaway Envelope
Operational radius (blue) versus worst-case flyaway envelope (red dashed; aircraft endurance × max airspeed = 57.96 km). Nearby aerodromes, hospitals, police stations, and military installations are shown as points of interest within the envelope so the PIC and approver can see what lies inside the worst-case footprint, even though the operational area is a small fraction of it.
12. RADIO FREQUENCIES AND CALL SCRIPTS
| Monitoring Frequency | CTAF 123.500 MHz (FASS Sishen) |
| Default CTAF | 124.800 MHz (regional default if no specific aerodrome) |
| Monitoring Note | Monitor CTAF for the duration of operations. |
12.1 Pre-Flight Advisory Call
"Sishen Traffic, unmanned aircraft Zulu-Sierra Romeo-Papa-Alfa Zero-Zero-Four-Two, drone operations, rail corridor inspection, three hundred and ninety four feet AGL, beyond visual line of sight extending six point four kilometres north-east of Sishen, approximately ninety minutes, Zulu-Sierra Romeo-Papa-Alfa Zero-Zero-Four-Two."
12.2 In-Flight Advisory
"Sishen Traffic, Zulu-Sierra Romeo-Papa-Alfa Zero-Zero-Four-Two, currently active three hundred and ninety four feet AGL, four kilometres north-east of Sishen, Zulu-Sierra Romeo-Papa-Alfa Zero-Zero-Four-Two."
12.3 Post-Flight Call
"Sishen Traffic, Zulu-Sierra Romeo-Papa-Alfa Zero-Zero-Four-Two, drone operations complete, Zulu-Sierra Romeo-Papa-Alfa Zero-Zero-Four-Two."
13. EMERGENCY QUICK REFERENCE
| Scenario | Immediate PIC action | Notify |
| C2 link loss | Confirm lost-link auto-RTH activated; clear airspace at home; visual scan for return; abort recovery if home obstructed. | Observer chain; tenant ops on confirmed loss-of-control event. |
| Geofence breach | RTH triggered automatically; manual override only by PIC if RTH unsafe; visual track on backup display. | Tenant Safety Manager; SACAA via occurrence reporting if loss of control. |
| Aircraft impact / forced landing | Secure scene; persons-clearance check; battery / fire watch; preserve evidence; do not move airframe until photographed. | SAPS Kathu; Gamagara Fire Services; tenant Safety Manager; SACAA occurrence (within 24 h if reportable). |
| Manned-aircraft conflict | Descend to 30 m AGL clear of corridor; broadcast on CTAF; visual track of conflicting traffic; resume only after acknowledgement. | FASS CTAF; tenant ops. |
| Injury on ground | Land safely; render first aid; call ER24 (084 124); preserve scene. | ER24 / hospital; SAPS Kathu; tenant Safety Manager. |
| RF / spectrum interference suspected | Switch to backup link; if persistent, RTH and abort; record event. | ICASA channel; tenant ops. |
14. AERODROMES (within reach)
| ICAO | Name | Distance | Bearing | Elevation | Frequency |
| FASS | Sishen Airport | 0.1 km | N (002°) | 3848 ft AMSL | CTAF 123.500 |
| FAOF | Olifantshoek | 43.3 km | SW (217°) | -- | CTAF 124.800 |
| FALH | Lohatla Military | 44.1 km | S (167°) | 4500 ft AMSL | CTAF 124.800 (military advisory) |
| FAKU | Johan Pienaar (Kuruman) | 45.8 km | NE (062°) | 4382 ft AMSL | CTAF 124.800 |
15. PRE-FLIGHT CHECKLIST
Group A -- Environmental Recheck
[ ] Weather verified within VLOS / BVLOS limits (SAWS METAR/TAF)
[ ] NOTAMs verified via ATNS File2Fly (FACT, FAJA)
[ ] GNSS conditions acceptable (SANSA Kp < 5)
[ ] Operational window within civil twilight
[ ] No SIGMET / AIRMET directly affecting the operating area
PIC sign-off: [ ] CONFIRMED Date: Time:
Group B -- FOM and Conditions
[ ] FOM reviewed in full; all conditions understood
[ ] IMSAFE self-assessment completed -- fit to fly
[ ] Risk register reviewed; all hazards confirmed or override recorded
PIC sign-off: [ ] CONFIRMED
Group C -- Aircraft Readiness
[ ] Pre-flight inspection per OEM checklist
[ ] Battery ≥ 90% at launch; 20% reserve enforced
[ ] Storage media installed and verified
[ ] Home point set and verified on controller
[ ] RTH altitude set (130 m AGL)
PIC sign-off: [ ] CONFIRMED
Group D -- Mission and Safety Systems
[ ] Geofence loaded and verified
[ ] Mission waypoints loaded on controller
[ ] Lost-link procedure verified (RTH)
[ ] Low-battery RTH threshold set
PIC sign-off: [ ] CONFIRMED
Group E -- Site Assessment and Communications
[ ] Radio tuned to CTAF 123.500
[ ] Pre-flight CTAF advisory call made
[ ] Visual obstacle survey complete
[ ] Wind speed measured on site: ______ m/s
[ ] No uninvolved persons in operational area
PIC sign-off: [ ] CONFIRMED
Group F -- BVLOS / C2 specific
[ ] Primary C2 link RSSI verified at planned max range
[ ] Backup link (4G LTE) active and tested
[ ] Observer chain in position; comms-checked on CTAF or operator channel
[ ] Corridor sterility verified along route
[ ] Emergency landing sites confirmed accessible
PIC sign-off: [ ] CONFIRMED
Group G -- Emergency Equipment
[ ] First-aid kit on site and within validity
[ ] Fire extinguisher (suitable for Li-Po / electrical) on site
[ ] Casualty evacuation plan confirmed (Kathu Private Hospital)
[ ] Spill / battery containment kit on site
PIC sign-off: [ ] CONFIRMED
Group H -- Sensitivities
[ ] Nature reserves / conservation areas checked
[ ] Schools / hospitals / sensitive facilities checked
[ ] Strategic / military installations checked
[ ] Power infrastructure checked
[ ] Pre-assessed results confirmed; deviations recorded:
PIC sign-off: [ ] CONFIRMED
16. PILOT SELF-HEALTH ASSESSMENT (IMSAFE)
| Factor | Assessment |
| I -- Illness | No illness or symptom affecting performance |
| M -- Medication | No medication impairing judgement or coordination |
| S -- Stress | No significant stress that could distract |
| A -- Alcohol | No alcohol within past 8 hours |
| F -- Fatigue | Adequately rested (minimum 8 hours sleep) |
| E -- Eating | Adequately nourished and hydrated |
PIC declaration: [ ] FIT TO FLY Date: Time:
17. TENANT MISSION-APPROVER DECISION
Internal mission approval is granted only by the tenant's authorised mission approver. Approval is a separate workflow event from the FlightDocket recommendation; it has its own actor and timestamp.
Decision: approved_for_pic_review
Approver: M. Raath, Mission Approver (Safety Manager) -- tenant role bound -- actor_id redacted
Decision Timestamp: 2026-05-08T05:42:11+02:00 SAST
Pre-conditions confirmed:
[x] all hard blockers closed [x] residual warnings accepted [x] permissions valid
[x] FOM complete [x] risk level acceptable [x] PIC / aircraft / area within authority
[x] documents ready for device sync
Approver signature:
Notes:
18. FOM DEVICE-SYNC CONFIRMATION
| Recipient | Role | Device ID | FOM Hash Match | Synced At | Status |
| J.A. Raath | PIC | DEV-PIC-redacted | match | 2026-05-08T05:48:03+02:00 | synced |
| M. Raath | Observer 1 | DEV-OBS-redacted | match | 2026-05-08T05:48:09+02:00 | synced |
19. PIC MISSION-OPENING DECLARATION
This is the final on-site gate. The mission may not commence until the PIC opens it.
Opening = approval. Opening the mission on the field client constitutes the PIC's formal acceptance and approval of the mission as briefed. The open action — actor identity, device ID, geolocation, FOM version / hash and timestamp — is recorded by the mobile app and written to the immutable audit trail. No separate PIC approval signature is required after the mission is opened.
I, the Pilot in Command, confirm that:
[ ] I have reviewed this Mission FOM in full;
[ ] current on-site conditions remain consistent with the FOM;
[ ] NOTAMs, airspace conditions, and permissions remain valid;
[ ] the aircraft and crew on site match the approved mission;
[ ] all required documents are present (per §7);
[ ] required emergency equipment is available (first aid, fire, evacuation plan);
[ ] I accept PIC responsibility for the operation as defined in CARs Part 101 §101.05.
PIC name:
RPL:
Device ID:
Date:
Time (SAST):
On-site location:
FOM version / hash acknowledged: v1 / 9f4c1e2a...e1d8e
Mission state on opening: pic_opened
PIC digital signature: auto-captured by the field client when the PIC opens the mission (actor, device ID, geolocation, FOM hash, timestamp written to the immutable audit trail).
20. POST-FLIGHT / CLOSURE
[ ] Post-flight CTAF call made
[ ] Aircraft secured; storage media removed; battery state recorded
[ ] Flight folio updated
[ ] Deviations from FOM recorded:
[ ] Incidents / defects recorded (if any):
[ ] SACAA occurrence report (if reportable per Part 12) -- submitted on:
[ ] Mission state: closed or aborted
PIC sign-off: Time:
21. AUDIT TRAIL AND DATA PROVENANCE
21.1 Immutable Identifiers
FOM is an Operate artefact. The Apply-side case_id (UASOC application lifecycle: initial_application / continuation / reactivation / renewal) is not bound to a live mission and is not recorded here. Authority to fly is the operator's UASOC + OpSpec, both already issued and reflected as references below.
| Tenant (Operator) ID | redacted (specimen) |
| UASOC Reference | UASOC-SPEC-XXX |
| OpSpec Reference | OPSPEC-2025-04 / line BVLOS-001 |
| Mission ID | 11111111-2222-3333-4444-555555555555 |
| Aircraft ID (canonical) | AC-ZS-RPA-0042 / snapshot SNAP-2026-05-08-001 |
| AMP Reference | AMP-Rev-04 |
| Flight Folio Reference | FF-2026-0142 |
| PIC actor ID | redacted |
| Mission Approver actor ID | redacted |
| Source Registry Version | regulatory-corpus-v2026-04 (effective 2026-04-15) |
| FOM Template Version | OM-A5-Template v3.2 |
| FOM Version | v1 |
| Output Hash (SHA-256) | 9f4c1e2a6b8d3f70e5b91d2c8a4f6b1e3d7c0f25a9e8b46d12fa370c5b4e1d8e |
21.2 State-Change Timeline
| Event | State | Actor | Timestamp (SAST) |
| Inputs validated | inputs_validated | FlightDocket Operate | 2026-05-08T05:30:00+02:00 |
| System recommendation issued | system_recommendation_only | FlightDocket Operate | 2026-05-08T05:30:01+02:00 |
| Tenant mission approval | tenant_approved_for_pic_review | M. Raath (Mission Approver) | 2026-05-08T05:42:11+02:00 |
| FOM synced to PIC | synced_to_pic | FlightDocket Operate | 2026-05-08T05:48:03+02:00 |
| PIC mission opening | awaiting_pic_open | J.A. Raath (PIC) | -- |
| Mission close / abort | pending | -- | -- |
21.3 Source Provenance (South African sources only)
| Source | Type | Status | Retrieved (SAST) | Duration |
| SAWS Aviation Weather (METAR / TAF) | weather | OK | 2026-05-08T05:25:00 | 612 ms |
| ATNS File2Fly (NOTAM) | NOTAM | OK | 2026-05-08T04:55:00 | 431 ms |
| ATNS SIGMET / AIRMET (FACT, FAJA) | SIGMET | OK | 2026-05-08T05:25:00 | 289 ms |
| SACAA Aerodrome Directory | aerodrome | OK | 2026-05-07T12:00:00 | cached |
| SANSA Space Weather (Kp) | space weather | OK | 2026-05-08T05:00:00 | 178 ms |
| Tenant document registry | permissions / docs | OK | 2026-05-08T05:30:00 | 92 ms |
| Operator flight-log archive | C2 / range evidence | OK | 2026-05-08T05:30:00 | 54 ms |
21.4 Data-Quality Blockers Cleared
Tenant approval and PIC opening would have been blocked by any of the following data-quality blockers:
| Blocker | This mission |
| Foreign / irrelevant weather or SIGMET data | cleared Only FACT / FAJA accepted; foreign WSUS-prefixed products filtered. |
| Missing emergency contact numbers | cleared No not_available rows present. |
| Conflicting aircraft identity | cleared Single canonical snapshot (DJI Matrice 350 RTK / ZS-RPA-0042). |
| Unverified BVLOS authority | cleared OpSpec BVLOS-001 + aircraft authorisation + C2 evidence verified. |
| Unverified aerodrome-proximity decision | cleared CTAF advisory route published; coordination required and recorded. |
| Expired volatile data | cleared Weather / NOTAM retrieved < 6 h before mission window. |
| Missing permissions | cleared All applicable permissions verified (§6). |
| Invalid crew / aircraft status | cleared RPL valid; Class 3 medical valid; AMP released-to-service. |
| Absent required emergency equipment | cleared First-aid + fire + evac plan + battery containment confirmed (Group G). |