37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 325077 |
Time | |
Date | 199601 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : djb |
State Reference | OH |
Altitude | msl bound lower : 14000 msl bound upper : 14000 |
Environment | |
Flight Conditions | IMC |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | artcc : zob |
Operator | general aviation : corporate |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 91 |
Flight Phase | descent other |
Route In Use | arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : cfi pilot : atp pilot : commercial |
Experience | flight time last 90 days : 60 flight time total : 4670 flight time type : 260 |
ASRS Report | 325077 |
Person 2 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course flight crew : overcame equipment problem |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Just passing djb VOR on junkr 1 arrival using GPS. Junkr intersection was either not programmed or missed because instead of autoplt/GPS navigation going to junkr intersection, we went direct to ptk. I was executing descent checklist and calling FBO at ptk (destination). PIC caught discrepancy and reprogrammed GPS to navigation to junkr intersection. No conflict, nothing said by center. I believe that the role of distrs or non-flying duties should be emphasized in 'CRM PNF awareness sits.' to use an effective instrument scan as an example: PNF should have a 'duties scan,' 'responsibility scan,' etc. No matter what other related duties you have, proper situational awareness demands you constantly ask yourself 'is the important stuff being done correctly?' don't assume anything.
Original NASA ASRS Text
Title: THE RPTR INVOLVED IN NON-FLYING DUTIES MISSED THE ERROR PROGRAMMED INTO THE GPS. THE RPTR SUGGESTS SPECIAL SCAN TRAINING ALONG WITH CRM THAT WOULD ASSURE PRIMARY REQUIREMENTS FOR GUIDING THE ACFT ARE ATTENDED TO.
Narrative: JUST PASSING DJB VOR ON JUNKR 1 ARR USING GPS. JUNKR INTXN WAS EITHER NOT PROGRAMMED OR MISSED BECAUSE INSTEAD OF AUTOPLT/GPS NAV GOING TO JUNKR INTXN, WE WENT DIRECT TO PTK. I WAS EXECUTING DSCNT CHKLIST AND CALLING FBO AT PTK (DEST). PIC CAUGHT DISCREPANCY AND REPROGRAMMED GPS TO NAV TO JUNKR INTXN. NO CONFLICT, NOTHING SAID BY CTR. I BELIEVE THAT THE ROLE OF DISTRS OR NON-FLYING DUTIES SHOULD BE EMPHASIZED IN 'CRM PNF AWARENESS SITS.' TO USE AN EFFECTIVE INST SCAN AS AN EXAMPLE: PNF SHOULD HAVE A 'DUTIES SCAN,' 'RESPONSIBILITY SCAN,' ETC. NO MATTER WHAT OTHER RELATED DUTIES YOU HAVE, PROPER SITUATIONAL AWARENESS DEMANDS YOU CONSTANTLY ASK YOURSELF 'IS THE IMPORTANT STUFF BEING DONE CORRECTLY?' DON'T ASSUME ANYTHING.
Data retrieved from NASA's ASRS site as of July 2007 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.