 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flawed execution of FMS programming protocol resulted in the loss of nav data and a track deviation for a crj-200 flight crew.
| Attributes | |
| ACN | 912357 |
| Time | |
| Date | 201010 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PHL.Airport |
| State Reference | PA |
| Environment | |
| Flight Conditions | IMC |
| Aircraft 1 | |
| Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Commercial |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I (pilot not flying) loaded the 9R approach into the FMS and informed the captain. While we were tracking on V16 to vcn; the captain went ahead and executed the approach on the FMS without asking to confirm. By doing so; the entire flight plan was cleared out of the FMS. As he executed; I stated 'no!' and quickly went to heading mode for him.he tried to put the flight route back in the FMS. ATC asked if we were on the victor airway. I replied that we were probably not and needed a heading until we fixed the FMS. He gave us a heading; then gave us direct vcn when able. To prevent this from happening again; I believe better communication between pilots is imperative. Especially; dealing with route changes in the FMS.
Original NASA ASRS Text
Title: Flawed execution of FMS programming protocol resulted in the loss of nav data and a track deviation for a CRJ-200 Flight Crew.
Narrative: I (pilot not flying) loaded the 9R approach into the FMS and informed the Captain. While we were tracking on V16 to VCN; the Captain went ahead and executed the approach on the FMS without asking to confirm. By doing so; the entire flight plan was cleared out of the FMS. As he executed; I stated 'No!' and quickly went to heading mode for him.He tried to put the flight route back in the FMS. ATC asked if we were on the victor airway. I replied that we were probably not and needed a heading until we fixed the FMS. He gave us a heading; then gave us direct VCN when able. To prevent this from happening again; I believe better communication between pilots is imperative. Especially; dealing with route changes in the FMS.
Data retrieved from NASA's ASRS site as of April 2012 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.