 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A pilot whose aircraft had panel mounted LORAN; GPS and VOR navigation capabilities penetrated R6302A because he was navigating on his hand held smart phone with GPS software which did not display the restricted airspace.
| Attributes | |
| ACN | 942384 |
| Time | |
| Date | 201104 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | GOP.Airport |
| State Reference | TX |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft High Wing 1 Eng Retractable Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | VFR Route |
| Flight Plan | None |
| Component | |
| Aircraft Component | GPS & Other Satellite Navigation |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Commercial |
| Experience | Flight Crew Last 90 Days 5 Flight Crew Total 11000 Flight Crew Type 100 |
| Events | |
| Anomaly | Airspace Violation All Types Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
Narrative:
Loss of situational awareness; using new smart phone GPS navigation program on direct flight and didn't pay enough attention to the primary GPS and map. [I] had checked different navigation pages on phone program. Looked back to primary panel mount and GPS and saw warning message for restricted airspace R6302A. I immediately knew where I was and turned away from restricted airspace; then proceeded to exit boundary. When sufficiently clear turned to a heading to fly around restricted area then continued on course. Have flown this route numerous times; knew the restricted area was there but the program on the phone doesn't show restricted or other airspace. I won't let my attention be diverted again. My normal navigation was to use a panel mounted LORAN; the panel mount GPS and to cross check VOR's on the route of flight. Cavu day and just watching the panel mount and moving map on the phone program contributed to an error on navigate.
Original NASA ASRS Text
Title: A pilot whose aircraft had panel mounted LORAN; GPS and VOR navigation capabilities penetrated R6302A because he was navigating on his hand held smart phone with GPS software which did not display the restricted airspace.
Narrative: Loss of situational awareness; using new smart phone GPS navigation program on direct flight and didn't pay enough attention to the primary GPS and map. [I] had checked different navigation pages on phone program. Looked back to primary panel mount and GPS and saw warning message for restricted airspace R6302A. I immediately knew where I was and turned away from restricted airspace; then proceeded to exit boundary. When sufficiently clear turned to a heading to fly around restricted area then continued on course. Have flown this route numerous times; knew the restricted area was there but the program on the phone doesn't show restricted or other airspace. I won't let my attention be diverted again. My normal navigation was to use a panel mounted LORAN; the panel mount GPS and to cross check VOR's on the route of flight. CAVU day and just watching the panel mount and moving map on the phone program contributed to an error on navigate.
Data retrieved from NASA's ASRS site as of April 2012 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.