 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A SR22 had a track deviation because the on board garmin 430 was improperly programed from ipad data because the ipad settings did not include intermediate VOR's on the airway.
| Attributes | |
| ACN | 934431 |
| Time | |
| Date | 201102 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | GPS & Other Satellite Navigation |
| Person 1 | |
| Function | Instructor |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Flight Instructor |
| Experience | Flight Crew Last 90 Days 150 Flight Crew Total 9500 Flight Crew Type 8 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
On an instrument training flight we had departed IMC within our void time. Our routing was put into the garmin 430 by my student and owner of the aircraft. This unit requires all fixes to be manually entered. One intersection was missed along the victor airway and resulted in the wrong track being followed. The controller caught this within 10 NM of the VOR and turned us toward the correct course. We continued and the flight continued uneventfully with no conflicting traffic. The problem arose because the airway was read from an ipad and the settings menu was not set to include fixes between VOR's. In an effort to meet a void time this was not double checked and the intersection that defined the airway was not included. The routing will be double checked in the future.
Original NASA ASRS Text
Title: A SR22 had a track deviation because the on board Garmin 430 was improperly programed from iPad data because the iPad settings did not include intermediate VOR's on the airway.
Narrative: On an instrument training flight we had departed IMC within our void time. Our routing was put into the Garmin 430 by my student and owner of the aircraft. This unit requires all fixes to be manually entered. One intersection was missed along the victor airway and resulted in the wrong track being followed. The Controller caught this within 10 NM of the VOR and turned us toward the correct course. We continued and the flight continued uneventfully with no conflicting traffic. The problem arose because the airway was read from an iPad and the settings menu was not set to include fixes between VOR's. In an effort to meet a void time this was not double checked and the intersection that defined the airway was not included. The routing will be double checked in the future.
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.