 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
GA pilot reported inadvertently entering a tfr when the tfr failed to display on his foreflight-equipped ipad.
| Attributes | |
| ACN | 1756411 |
| Time | |
| Date | 202007 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Direct |
| Flight Plan | None |
| Component | |
| Aircraft Component | Electronic Flt Bag (EFB) |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 20 Flight Crew Total 750 Flight Crew Type 70 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Airspace Violation All Types |
Narrative:
I packed my foreflight trip on my ipad and headed from ZZZ1 - ZZZ. I picked up flight following as I left ZZZ1 in order to climb through ZZZ2 airspace. I leveled off at 4;500 feet and stayed with ZZZ approach for about 50 miles. I proceeded to cancel flight following and flew down the X river en route to ZZZ. Foreflight did not notify me of the tfr. When I landed at ZZZ airport; the airport manager gave me a number to call for intruding on the tfr. I've flown this exact route dozens of times and filed flight plans or picked-up flight following every time a tfr was in effect. When I called the number given to me by the airport manager; I was told that I was the second person that night that said foreflight was not reporting/displaying tfrs. I'm concerned that there may be a bug in foreflight that is causing the software to fail to display tfrs. I will cross check with wingx pro to ensure tfr status before flying this route again; and I'll maintain VFR flight filing to mitigate this risk in the future. I'm filing this report in case there's an issue with foreflight not connecting with the tfr database and properly displaying tfrs on the foreflight map.
Original NASA ASRS Text
Title: GA pilot reported inadvertently entering a TFR when the TFR failed to display on his ForeFlight-equipped iPad.
Narrative: I packed my ForeFlight trip on my iPad and headed from ZZZ1 - ZZZ. I picked up flight following as I left ZZZ1 in order to climb through ZZZ2 airspace. I leveled off at 4;500 feet and stayed with ZZZ Approach for about 50 miles. I proceeded to cancel flight following and flew down the X River en route to ZZZ. ForeFlight did not notify me of the TFR. When I landed at ZZZ airport; the Airport Manager gave me a number to call for intruding on the TFR. I've flown this exact route dozens of times and filed flight plans or picked-up flight following every time a TFR was in effect. When I called the number given to me by the airport manager; I was told that I was the second person that night that said ForeFlight was not reporting/displaying TFRs. I'm concerned that there may be a bug in ForeFlight that is causing the software to fail to display TFRs. I will cross check with WingX Pro to ensure TFR status before flying this route again; and I'll maintain VFR flight filing to mitigate this risk in the future. I'm filing this report in case there's an issue with ForeFlight not connecting with the TFR database and properly displaying TFRs on the ForeFlight map.
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.