37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1604809 |
Time | |
Date | 201812 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MHV.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Direct |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 10 Flight Crew Total 6000 Flight Crew Type 800 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
On a VFR flight to L71 at 4000 MSL/1300 AGL I contacted mhv (mojave) tower from a position approximately 6 miles ssw of that airport for permission to transit their class C airspace. The tower controller inquired if I was aware of a tfr which impacted their facility. I was not; and although I had both foreflight fed by ads-B/in running on an ipad and a GPS with xm weather; both of which display tfrs; neither was showing any. Uncertain what the situation was; I immediately reversed course and on the advice of the tower controller contacted joshua approach; who also seemed somewhat uncertain about the status of the tfr; but after some consultation with his supervisor advised me he could clear me through to my destination if I could complete the flight within 15 minutes. I could and he did. While I do not believe I initially penetrated the tfr prior to contacting the tower controller and was subsequently cleared through it by joshua; some days later I received a phone call from a friend who in turn had spoken casually with another individual who asked if he knew [my name] flying [aircraft n-number] and said he had noted my ads-B return inside the tfr. Hence this report. The situation was somewhat unusual as I have come to depend on the 'live' airspace depictions and find them very dependable. I suspect the tfr was somehow not distributed in the same way as normal tfrs. In any case; I will start making it a habit to download a formal briefing.
Original NASA ASRS Text
Title: GA Pilot reported nonstandard TFR dissemination resulting in TFR violation.
Narrative: On a VFR flight to L71 at 4000 MSL/1300 AGL I contacted MHV (Mojave) Tower from a position approximately 6 miles SSW of that airport for permission to transit their Class C airspace. The Tower Controller inquired if I was aware of a TFR which impacted their facility. I was not; and although I had both ForeFlight fed by ADS-B/in running on an iPad and a GPS with XM weather; both of which display TFRs; neither was showing any. Uncertain what the situation was; I immediately reversed course and on the advice of the Tower Controller contacted Joshua Approach; who also seemed somewhat uncertain about the status of the TFR; but after some consultation with his supervisor advised me he could clear me through to my destination if I could complete the flight within 15 minutes. I could and he did. While I do not believe I initially penetrated the TFR prior to contacting the Tower Controller and was subsequently cleared through it by Joshua; some days later I received a phone call from a friend who in turn had spoken casually with another individual who asked if he knew [my name] flying [aircraft N-number] and said he had noted my ADS-B return inside the TFR. Hence this report. The situation was somewhat unusual as I have come to depend on the 'live' airspace depictions and find them very dependable. I suspect the TFR was somehow not distributed in the same way as normal TFRs. In any case; I will start making it a habit to download a formal briefing.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.