37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1529244 |
Time | |
Date | 201803 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | MLB.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-32 Cherokee Six/Lance/Saratoga/6X |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 25 Flight Crew Total 2700 Flight Crew Type 1700 |
Events | |
Anomaly | Airspace Violation All Types |
Narrative:
I obtained briefing using foreflight program. Flew to sua with plans to circumnavigate the mlb tfr. The display mode for the foreflight was in relatively close range so the upcoming tfr was not visible. On autopilot.I discovered a new function on the foreflight program - 'glide bubble' - and began setting it up which required referencing the pilot operating handbook and doing conversions to compute the glide ratio. I used the ipad calculator apps and exited the foreflight app to do so. Hence; I did not 'see' the upcoming intrusion. Then; before completing the task; a 2 1/2 year old passenger had an episode of diarrhea that overflowed his diaper. I tried to assist my other passenger who was in 'the back' as best I could. This further delayed my returning to and viewing of the foreflight moving map. In addition; there was a strong tail wind.when I returned to the foreflight map page; I had entered and was 2/3 through the tfr. I was contacting pbi approach for a squawk for landing at sua as advised by the ATIS due to the presidential tfr near sua. I was asked to contact orlando approach by phone after landing. Uneventful approach and landing at sualessons learned: plan route with waypoints planned and program them into GPS to avoid areas of conflict do not divert attention for extended periods from flight duties - even to enable a safety feature - no matter how beneficial it may be for future flights! Do it on the ground [and] use flight following.
Original NASA ASRS Text
Title: PA-32R pilot reported a TFR airspace incursion resulted when he became distracted from his navigational duties.
Narrative: I obtained briefing using ForeFlight program. Flew to SUA with plans to circumnavigate the MLB TFR. The display mode for the ForeFlight was in relatively close range so the upcoming TFR was not visible. On autopilot.I discovered a new function on the ForeFlight program - 'glide bubble' - and began setting it up which required referencing the Pilot Operating Handbook and doing conversions to compute the glide ratio. I used the iPad calculator apps and exited the ForeFlight app to do so. Hence; I did not 'see' the upcoming intrusion. Then; before completing the task; a 2 1/2 year old passenger had an episode of diarrhea that overflowed his diaper. I tried to assist my other passenger who was in 'the back' as best I could. This further delayed my returning to and viewing of the ForeFlight moving map. In addition; there was a strong tail wind.When I returned to the ForeFlight map page; I had entered and was 2/3 through the TFR. I was contacting PBI approach for a squawk for landing at SUA as advised by the ATIS due to the presidential TFR near SUA. I was asked to contact Orlando approach by phone after landing. Uneventful approach and landing at SUALessons learned: Plan route with waypoints planned and program them into GPS to avoid areas of conflict do not divert attention for extended periods from flight duties - even to enable a safety feature - no matter how beneficial it may be for future flights! Do it on the ground [and] use flight following.
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.