ASRS 1866179
ACN 1866179 · 2021-12 · DJI Mavic 3
UAS pilot reported they unknowingly flew their UAS into a TFR. Reporter stated there were no TFRs prior to launch and the TFR became active during the flight.
Pilot narrative
Verbatim, de-identified by NASA. Placeholders: ZZZ,
X, Y.
Got prior authorization through the Aloft App. Confirmed no TFR on B4Ufly app. Flight started at XA:45am. TFR went into effect at XB:00am. I landed at XB:24am and unknowingly violated the TFR as flight was in progress when TFR went into effect. I checked two official sources and the DJI geofence did not notify when a TFR went up. I made every attempt to fly legally. There were no active fire operations, no active air operations and the airspace was clear of all aircraft. Upon realization, I opted to self report.
Analyst callback
Paraphrased notes from ASRS analyst follow-up calls with the reporter.
Reporter stated they looked at B4UFLY and the DJI app prior to launch to check for TFRs and NOTAMs. There were none showing at the time of launch nor planned in the several hours after the launch. Several hours after landing the UAS, the Pilot learned of the TFR. The UAS Pilot spoke with the FAA and learned the TFR was issued directly from a nearby ATC Tower and this is why it wasn't posted prior to becoming active.
NASA classification · Anomalies
- Airspace Violation
- Deviation / Discrepancy - Procedural
NASA classification · Assessments
- Contributing Factors / Situations
- Chart Or Publication · Procedure
- Primary Problem
- Ambiguous
ASRS reports are voluntary, de-identified by NASA, and represent the reporter's perspective; they are not investigated and cannot be used to infer prevalence. Authoritative source: asrs.arc.nasa.gov ↗