37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1609857 |
Time | |
Date | 201901 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | DTW.Airport |
State Reference | MI |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
On our flight release we were filed to fly to rkcty and then the RKCTY1 arrival to detroit. I loaded this into the FMS. When we received our clearance from ATC; they cleared us to rkcty and then the KKISS1 arrival; but I never changed it in the FMS. We took off and navigated to rkcty and didn't realize I had programmed the wrong arrival until they cleared us to stley; which is a fix on the KKISS1. We reprogrammed the FMS and navigated as directed with no further issuesi believe there were several factors: multiple arrivals utilizing the same fix is a threat in itself. In addition to this; we were on leg 5 on day 4 of our 4 day trip. We also had a drunk passenger that we didn't allow on board; and I think that contributed to distraction during the preparation phase of our flight. Not using the same fix on multiple arrivals would help eliminate confusion for arrivals. Also I should have verified all the fixes on the arrival as part of my briefing.
Original NASA ASRS Text
Title: CRJ-200 Captain reported a track deviation occurred on the arrival into DTW; due in part to fatigue and distractions.
Narrative: On our flight release we were filed to fly to RKCTY and then the RKCTY1 arrival to Detroit. I loaded this into the FMS. When we received our clearance from ATC; they cleared us to RKCTY and then the KKISS1 arrival; but I never changed it in the FMS. We took off and navigated to RKCTY and didn't realize I had programmed the wrong arrival until they cleared us to STLEY; which is a fix on the KKISS1. We reprogrammed the FMS and navigated as directed with no further issuesI believe there were several factors: multiple arrivals utilizing the same fix is a threat in itself. In addition to this; we were on leg 5 on day 4 of our 4 day trip. We also had a drunk passenger that we didn't allow on board; and I think that contributed to distraction during the preparation phase of our flight. Not using the same fix on multiple arrivals would help eliminate confusion for arrivals. Also I should have verified all the fixes on the arrival as part of my briefing.
Data retrieved from NASA's ASRS site 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.