 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
The captain of an A321 failed to note when his first officer; new to the airline; loaded the route in the FMS incorrectly. A track deviation ensued.
| Attributes | |
| ACN | 1090135 |
| Time | |
| Date | 201305 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZDC.ARTCC |
| State Reference | VA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | A321 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types Flight Deck / Cabin / Aircraft Event Other / Unknown |
Narrative:
We got our clearance and verified the route. My first officer; who was new to the airplane and the company; entered the route into the FMS. I read the information that was in the FMS and the first officer looked at the information on the release and ATC clearance. Little did I know that he had misread both our release flight plan and the actual clearance (which was the same as our filed route.) the file route looked like this: kclt MERIL6 meril rdu J207 fkn J79 joani J79 jfk krann kbos. What was entered in the FMS was: fkn joani J79 jfk KRANN3 [kbos.] I read back what was in the FMS which got an affirmative response from the pilot flying. It wasn't until just after fkn that we found out that the route which had been entered was incorrect. The controller cleared us to salisbury and we were back on the correct course; a four mile deviation.we captains need to be reminded that the person sitting next to us may not have been at this airline for 20 years or more. There may be some confusion with day to day operations; as there was in this case. Had I been more proactive; I could have caught our error. When I read our route back during the verification process; I hesitated at the part that said fkn joani; that didn't sound right to me. When I got an affirmative response from the first officer...I moved on. Next time I won't.
Original NASA ASRS Text
Title: The Captain of an A321 failed to note when his First Officer; new to the airline; loaded the route in the FMS incorrectly. A track deviation ensued.
Narrative: We got our clearance and verified the route. My First Officer; who was new to the Airplane and the Company; entered the route into the FMS. I read the information that was in the FMS and the First Officer looked at the information on the release and ATC clearance. Little did I know that he had misread both our release flight plan and the actual clearance (which was the same as our filed route.) The file route looked like this: KCLT MERIL6 MERIL RDU J207 FKN J79 JOANI J79 JFK KRANN KBOS. What was entered in the FMS was: FKN JOANI J79 JFK KRANN3 [KBOS.] I read back what was in the FMS which got an affirmative response from the pilot flying. It wasn't until just after FKN that we found out that the route which had been entered was incorrect. The Controller cleared us to Salisbury and we were back on the correct course; a four mile deviation.We captains need to be reminded that the person sitting next to us may not have been at this airline for 20 years or more. There may be some confusion with day to day operations; as there was in this case. Had I been more proactive; I could have caught our error. When I read our route back during the verification process; I hesitated at the part that said FKN JOANI; that didn't sound right to me. When I got an affirmative response from the First Officer...I moved on. Next time I won't.
Data retrieved from NASA's ASRS site as of July 2013 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.