37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1211522 |
Time | |
Date | 201410 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | AUN.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Direct |
Flight Plan | None |
Person 1 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 42 Flight Crew Total 1136 Flight Crew Type 1136 |
Events | |
Anomaly | Airspace Violation All Types |
Narrative:
There was a firefighting tfr in the vicinity of colfax; ca that had been in effect [for several days]. The western edge of the tfr was just off the eastern end of runway 25 at aun; necessitating landing on runway 7; even though the winds favored 25. I confirmed the tfr was still in effect using a ground-based pc prior to takeoff. In the air; however; it wasn't visible on my mfd even though other tfrs in the area were; (the mfd uses xm satellite weather as its tfr data source). I contacted FSS in the air and they confirmed the tfr was still in effect; though we didn't discuss the precise boundaries. As I approached aun I monitored traffic on the CTAF and everyone was using 25. When I asked about the tfr I was told it had moved far enough away from 25 to allow its use. Because of this; and because other traffic was using 25; I chose to land on 25. Because I couldn't see the tfr; though; it's possible I briefly penetrated it while on my base and final approach legs.
Original NASA ASRS Text
Title: SR22 pilot believes he may have entered a firefighting TFR while on base and final for Runway 25 at AUN. The existence of the TFR was confirmed with FSS but the TFR would not display on the aircraft MFD.
Narrative: There was a firefighting TFR in the vicinity of Colfax; CA that had been in effect [for several days]. The western edge of the TFR was just off the eastern end of runway 25 at AUN; necessitating landing on runway 7; even though the winds favored 25. I confirmed the TFR was still in effect using a ground-based PC prior to takeoff. In the air; however; it wasn't visible on my MFD even though other TFRs in the area were; (the MFD uses XM satellite weather as its TFR data source). I contacted FSS in the air and they confirmed the TFR was still in effect; though we didn't discuss the precise boundaries. As I approached AUN I monitored traffic on the CTAF and everyone was using 25. When I asked about the TFR I was told it had moved far enough away from 25 to allow its use. Because of this; and because other traffic was using 25; I chose to land on 25. Because I couldn't see the TFR; though; it's possible I briefly penetrated it while on my base and final approach legs.
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.