 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A general aviation pilot reports inadvertently entering a tfr and landing at the nearest airport when a call is heard on guard frequency. An ipad with foreflight application was used for planning and enroute navigation; but tfr did not appear.
| Attributes | |
| ACN | 1009732 |
| Time | |
| Date | 201205 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | Marginal |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | None |
| Person 1 | |
| Function | Single Pilot Pilot Flying |
| Qualification | Flight Crew Multiengine Flight Crew Private |
| Experience | Flight Crew Last 90 Days 25 Flight Crew Total 420 Flight Crew Type 370 |
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural FAR |
Narrative:
[I] waited for weather to clear before setting off. Flying under cloud layer; VFR and inadvertently violated tfr airspace. Regular commuting route for low weather; flight planned and weather checked along route using foreflight for ipad; but tfr was not displayed. Monitoring guard frequency I heard a garbled call for an airspace violation with a heading of 090; I was on 270 heading. Reviewed airspace and realized a tfr may be in effect; decided to divert to closest airport. Called the tower and landed without incident.
Original NASA ASRS Text
Title: A general aviation pilot reports inadvertently entering a TFR and landing at the nearest airport when a call is heard on guard frequency. An iPad with Foreflight application was used for planning and enroute navigation; but TFR did not appear.
Narrative: [I] waited for weather to clear before setting off. Flying under cloud layer; VFR and inadvertently violated TFR airspace. Regular commuting route for low weather; flight planned and weather checked along route using Foreflight for iPad; but TFR was not displayed. Monitoring guard frequency I heard a garbled call for an airspace violation with a heading of 090; I was on 270 heading. Reviewed airspace and realized a TFR may be in effect; decided to divert to closest airport. Called the Tower and landed without incident.
Data retrieved from NASA's ASRS site as of July 2013 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.