37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 672835 |
Time | |
Date | 200509 |
Place | |
Locale Reference | navaid : pxt.vortac |
State Reference | MD |
Altitude | msl single value : 9000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zdc.artcc |
Operator | general aviation : personal |
Make Model Name | M-20 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | cruise : level |
Route In Use | enroute airway : v229.airway |
Flight Plan | IFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 20 flight time total : 1300 flight time type : 1100 |
ASRS Report | 672835 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Events | |
Anomaly | non adherence : far non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : provided flight assist |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Aircraft Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
My routing from rome; GA; to atlantic city; nj; was amended en route. I was given the routing correctly by ATC and I copied it down correctly. However; when programming the GPS; I left out a waypoint. V229 has a dogleg and when programming the GPS; I omitted the intersection (gared; I think) that is the apex of the dogleg. So; when departing pxt VOR; I was on a more easterly heading than I should have been and came close to the pxt restr area and perhaps entered it. ATC called me with a vector back to the north which returned me to V229. This problem was caused by incorrect reading of the sectional chart which led me to assume that V229 was straight and caused me to omit gared intersection where it doglegs. Communication with ATC was not a factor. Callback conversation with reporter revealed the following information: reporter stated that this incident was totally pilot error. The GPS system does not list airways and; therefore; the operator must enter each NAVAID identify and then the waypoint between navaids if its track is not a straight line.
Original NASA ASRS Text
Title: AN M20 PLT USING A KLN 9B GPS NAV SYS FAILED TO ENTER A VICTOR AIRWAYS WAYPOINT AND MISSED A DOGLEG. HE APCHED A PXT RESTR AREA.
Narrative: MY ROUTING FROM ROME; GA; TO ATLANTIC CITY; NJ; WAS AMENDED ENRTE. I WAS GIVEN THE ROUTING CORRECTLY BY ATC AND I COPIED IT DOWN CORRECTLY. HOWEVER; WHEN PROGRAMMING THE GPS; I LEFT OUT A WAYPOINT. V229 HAS A DOGLEG AND WHEN PROGRAMMING THE GPS; I OMITTED THE INTXN (GARED; I THINK) THAT IS THE APEX OF THE DOGLEG. SO; WHEN DEPARTING PXT VOR; I WAS ON A MORE EASTERLY HDG THAN I SHOULD HAVE BEEN AND CAME CLOSE TO THE PXT RESTR AREA AND PERHAPS ENTERED IT. ATC CALLED ME WITH A VECTOR BACK TO THE N WHICH RETURNED ME TO V229. THIS PROB WAS CAUSED BY INCORRECT READING OF THE SECTIONAL CHART WHICH LED ME TO ASSUME THAT V229 WAS STRAIGHT AND CAUSED ME TO OMIT GARED INTXN WHERE IT DOGLEGS. COM WITH ATC WAS NOT A FACTOR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THIS INCIDENT WAS TOTALLY PLT ERROR. THE GPS SYS DOES NOT LIST AIRWAYS AND; THEREFORE; THE OPERATOR MUST ENTER EACH NAVAID IDENT AND THEN THE WAYPOINT BTWN NAVAIDS IF ITS TRACK IS NOT A STRAIGHT LINE.
Data retrieved from NASA's ASRS site as of January 2009 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.