37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 462400 |
Time | |
Date | 200001 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : n90.tracon |
State Reference | NY |
Altitude | msl single value : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : n90.tracon |
Operator | common carrier : charter |
Make Model Name | Gulfstream I (Large Turboprop) |
Operating Under FAR Part | Part 135 |
Navigation In Use | other |
Flight Phase | climbout : initial |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : instrument pilot : commercial pilot : atp |
Experience | flight time last 90 days : 75 flight time total : 5300 flight time type : 2300 |
ASRS Report | 462400 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
The first officer picked up our ATC clearance while I loaded and briefed our passenger. We had repositioned to teb the night before to avoid a major winter storm. I think we both may have been poorly rested (first night back out, worrisome WX, noisy hotel). Anyway, we discussed the departure, emphasized my concerns with the slippery txwys and runways, all was well, contacted tower and departed. Ny had given us a vector during the departure then instructed us to proceed direct to lanna intersection. We did. Unbeknownst to me was that the first officer had used an airway to feed our route into the FMS and was planning on using the VHF navigation on the right side to comply with the rest of the clearance. Upon receiving the instruction to proceed direct lanna, I selected FMS on the right side and announced that this was taking place. Again both of us a little tired perhaps, didn't realize that the FMS was only partially loaded and after crossing lanna was about to deviate from our clearance and take us to a left turn to join the wrong airway and interfere with other traffic off of ewr. The controller queried us on our clearance, we read it back, he issued a turn, I asked for confirmation and clarification. Upon receiving clarification I checked the flight plan in the FMS and asked first officer what he was trying to accomplish. First officer then explained the #2 VHF navigation had been set but had also misconstrued what had occurred with subsequent clearance to direct land, and my hard selecting the FMS as primary on the right side. Generally bad procedures, even with our familiarity with teb direct ewr, I should have taken more time to thoroughly brief the departure and had the chart out actually showing the relationship of lanna to the radial we were to next intercept. The data navigation was showing a flight plan but it showed an incorrect segment that had been loaded by the first officer to facilitate our en route navigation.
Original NASA ASRS Text
Title: CHARTER FLC EXPERIENCES A TRACK DEV DUE TO NAV SYS INPUT AND SELECTION ERROR.
Narrative: THE FO PICKED UP OUR ATC CLRNC WHILE I LOADED AND BRIEFED OUR PAX. WE HAD REPOSITIONED TO TEB THE NIGHT BEFORE TO AVOID A MAJOR WINTER STORM. I THINK WE BOTH MAY HAVE BEEN POORLY RESTED (FIRST NIGHT BACK OUT, WORRISOME WX, NOISY HOTEL). ANYWAY, WE DISCUSSED THE DEP, EMPHASIZED MY CONCERNS WITH THE SLIPPERY TXWYS AND RWYS, ALL WAS WELL, CONTACTED TWR AND DEPARTED. NY HAD GIVEN US A VECTOR DURING THE DEP THEN INSTRUCTED US TO PROCEED DIRECT TO LANNA INTXN. WE DID. UNBEKNOWNST TO ME WAS THAT THE FO HAD USED AN AIRWAY TO FEED OUR RTE INTO THE FMS AND WAS PLANNING ON USING THE VHF NAV ON THE R SIDE TO COMPLY WITH THE REST OF THE CLRNC. UPON RECEIVING THE INSTRUCTION TO PROCEED DIRECT LANNA, I SELECTED FMS ON THE R SIDE AND ANNOUNCED THAT THIS WAS TAKING PLACE. AGAIN BOTH OF US A LITTLE TIRED PERHAPS, DIDN'T REALIZE THAT THE FMS WAS ONLY PARTIALLY LOADED AND AFTER XING LANNA WAS ABOUT TO DEVIATE FROM OUR CLRNC AND TAKE US TO A L TURN TO JOIN THE WRONG AIRWAY AND INTERFERE WITH OTHER TFC OFF OF EWR. THE CTLR QUERIED US ON OUR CLRNC, WE READ IT BACK, HE ISSUED A TURN, I ASKED FOR CONFIRMATION AND CLARIFICATION. UPON RECEIVING CLARIFICATION I CHKED THE FLT PLAN IN THE FMS AND ASKED FO WHAT HE WAS TRYING TO ACCOMPLISH. FO THEN EXPLAINED THE #2 VHF NAV HAD BEEN SET BUT HAD ALSO MISCONSTRUED WHAT HAD OCCURRED WITH SUBSEQUENT CLRNC TO DIRECT LAND, AND MY HARD SELECTING THE FMS AS PRIMARY ON THE R SIDE. GENERALLY BAD PROCS, EVEN WITH OUR FAMILIARITY WITH TEB DIRECT EWR, I SHOULD HAVE TAKEN MORE TIME TO THOROUGHLY BRIEF THE DEP AND HAD THE CHART OUT ACTUALLY SHOWING THE RELATIONSHIP OF LANNA TO THE RADIAL WE WERE TO NEXT INTERCEPT. THE DATA NAV WAS SHOWING A FLT PLAN BUT IT SHOWED AN INCORRECT SEGMENT THAT HAD BEEN LOADED BY THE FO TO FACILITATE OUR ENRTE NAV.
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.