 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Falcon 50 corporate flight crew does not notice change in routing and programs the original route in the FMS.
| Attributes | |
| ACN | 336341 |
| Time | |
| Date | 199605 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : pom |
| State Reference | CA |
| Altitude | msl bound lower : 8000 msl bound upper : 8000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : ont |
| Operator | general aviation : corporate |
| Make Model Name | Falcon 50 |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | Other Other |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | departure sid : sid |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 90 flight time total : 6000 flight time type : 1000 |
| ASRS Report | 336341 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | non adherence : clearance non adherence : far non adherence : published procedure other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : became reoriented other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I filed an IFR flight plan through commercial service. The computer picked the hassa 4 departure with the dagget transition. When I picked up the clearance, the controller gave me the pomona 6 departure with the dagget transition. It just never registered that this was a change from what the computer said. I made a mistake and put the hassa 4 into the FMS. As we taxied out, the PF read the clearance as the pomona 6 departure. I still did not catch the mistake I made. We took off and proceeded to follow the hassa 4 departure. Departure control cleared us direct to pomona VOR and the rest of the pomona 6 departure. I read this back to him, but I still did not catch the fact that I had the hassa 4 programmed into the FMS. As we crossed the pomona VOR and started out on the radial for the hassa 4 the controller asked if we were on the pomona 6 departure. That is when I realized what I had done. I told him that we were on the hassa 4 departure. He gave us a vector and later cleared us direct to dagget without any incident. The controller seemed nice and helpful. I was only embarrassed that it took so long for me to catch my mistake. The problem I think came when I programmed the FMS instead of waiting for the PF to program it himself so that both of us could double-check our routing. From now on our policy is to verify the routing by having each person set up his side of the aircraft and checking each other if there are any discrepancies.
Original NASA ASRS Text
Title: FALCON 50 CORPORATE FLC DOES NOT NOTICE CHANGE IN ROUTING AND PROGRAMS THE ORIGINAL RTE IN THE FMS.
Narrative: I FILED AN IFR FLT PLAN THROUGH COMMERCIAL SVC. THE COMPUTER PICKED THE HASSA 4 DEP WITH THE DAGGET TRANSITION. WHEN I PICKED UP THE CLRNC, THE CTLR GAVE ME THE POMONA 6 DEP WITH THE DAGGET TRANSITION. IT JUST NEVER REGISTERED THAT THIS WAS A CHANGE FROM WHAT THE COMPUTER SAID. I MADE A MISTAKE AND PUT THE HASSA 4 INTO THE FMS. AS WE TAXIED OUT, THE PF READ THE CLRNC AS THE POMONA 6 DEP. I STILL DID NOT CATCH THE MISTAKE I MADE. WE TOOK OFF AND PROCEEDED TO FOLLOW THE HASSA 4 DEP. DEP CTL CLRED US DIRECT TO POMONA VOR AND THE REST OF THE POMONA 6 DEP. I READ THIS BACK TO HIM, BUT I STILL DID NOT CATCH THE FACT THAT I HAD THE HASSA 4 PROGRAMMED INTO THE FMS. AS WE CROSSED THE POMONA VOR AND STARTED OUT ON THE RADIAL FOR THE HASSA 4 THE CTLR ASKED IF WE WERE ON THE POMONA 6 DEP. THAT IS WHEN I REALIZED WHAT I HAD DONE. I TOLD HIM THAT WE WERE ON THE HASSA 4 DEP. HE GAVE US A VECTOR AND LATER CLRED US DIRECT TO DAGGET WITHOUT ANY INCIDENT. THE CTLR SEEMED NICE AND HELPFUL. I WAS ONLY EMBARRASSED THAT IT TOOK SO LONG FOR ME TO CATCH MY MISTAKE. THE PROB I THINK CAME WHEN I PROGRAMMED THE FMS INSTEAD OF WAITING FOR THE PF TO PROGRAM IT HIMSELF SO THAT BOTH OF US COULD DOUBLE-CHK OUR ROUTING. FROM NOW ON OUR POLICY IS TO VERIFY THE ROUTING BY HAVING EACH PERSON SET UP HIS SIDE OF THE ACFT AND CHKING EACH OTHER IF THERE ARE ANY DISCREPANCIES.
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.