 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
During a hurried turn around a standard route was entered into the FMC instead of the filed route. Cockpit checking routine is interrupted resulting in the incorrect route being flown after departure.
| Attributes | |
| ACN | 527540 |
| Time | |
| Date | 200110 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | intersection : laurn |
| State Reference | NY |
| Altitude | msl single value : 37000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | departure sid : swann |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : multi engine pilot : commercial |
| Experience | flight time last 90 days : 100 flight time total : 4000 flight time type : 1600 |
| ASRS Report | 527540 |
| Events | |
| Anomaly | non adherence : published procedure non adherence : company policies other spatial deviation |
| Resolutory Action | flight crew : became reoriented flight crew : returned to original clearance |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Route deviation. Departure from bwi. Due to hurried turnaround I failed to double check the filed route versus the standard route I had programmed into the FMC. The captain also failed to double check the route in the FMC. Our first indication of a problem occurred when ZNY center asked us about our course shortly after rbv on J222. Once we realized our error we changed course for dir alb and notified ZNY center of this. To my knowledge there were no conflicts due to this deviation. The rest of the flight was uneventful. I usually enter the route in the FMC and check it off the release at the same time. Occasionally, it takes a little while for the paperwork to get to me after we pull into the gate. In the past, in this type of situation, I usually enter the standard route and go back and double check it when I receive the release. This time I became distracted and rushed and failed to do so. In the future, I plan to wait until I receive the release prior to programming the FMC.
Original NASA ASRS Text
Title: DURING A HURRIED TURN AROUND A STANDARD RTE WAS ENTERED INTO THE FMC INSTEAD OF THE FILED RTE. COCKPIT CHKING ROUTINE IS INTERRUPTED RESULTING IN THE INCORRECT RTE BEING FLOWN AFTER DEP.
Narrative: RTE DEV. DEP FROM BWI. DUE TO HURRIED TURNAROUND I FAILED TO DOUBLE CHK THE FILED RTE VERSUS THE STANDARD RTE I HAD PROGRAMMED INTO THE FMC. THE CAPT ALSO FAILED TO DOUBLE CHK THE RTE IN THE FMC. OUR FIRST INDICATION OF A PROBLEM OCCURRED WHEN ZNY CENTER ASKED US ABOUT OUR COURSE SHORTLY AFTER RBV ON J222. ONCE WE REALIZED OUR ERROR WE CHANGED COURSE FOR DIR ALB AND NOTIFIED ZNY CENTER OF THIS. TO MY KNOWLEDGE THERE WERE NO CONFLICTS DUE TO THIS DEV. THE REST OF THE FLT WAS UNEVENTFUL. I USUALLY ENTER THE RTE IN THE FMC AND CHK IT OFF THE RELEASE AT THE SAME TIME. OCCASIONALLY, IT TAKES A LITTLE WHILE FOR THE PAPERWORK TO GET TO ME AFTER WE PULL INTO THE GATE. IN THE PAST, IN THIS TYPE OF SITUATION, I USUALLY ENTER THE STANDARD RTE AND GO BACK AND DOUBLE CHK IT WHEN I RECEIVE THE RELEASE. THIS TIME I BECAME DISTRACTED AND RUSHED AND FAILED TO DO SO. IN THE FUTURE, I PLAN TO WAIT UNTIL I RECEIVE THE RELEASE PRIOR TO PROGRAMMING THE FMC.
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.