 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported a heading deviation due to similar fix names.
| Attributes | |
| ACN | 1582804 |
| Time | |
| Date | 201810 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | SEA.Airport |
| State Reference | WA |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I was captain and the pm (pilot monitoring) on this leg. Sea was a mess due to a closed runway and taxiways. We paid particular attention to the taxi out and it went perfect. We took off 34C flying the SUMMA1 departure. Passing summa seattle center cleared us to direct to kotaa. I typed in kotta and went to 'plan' mode and had first officer (first officer) (PF [pilot flying]) 'verify'; which he did. I executed it and selected LNAV. We were basically heading straight to kotta. ATC queried us as to our heading and then cleared us to our filed route. We proceeded [to the route] and completed the flight.event occurred because I typed in the incorrect fix and we both believed it was correct. The two fixes are kotaa (correct fix for us) and kotta (incorrect fix for us but close enough to be confusing). I should have had the IFR page up with our route and all waypoints selected and cross referenced it. Additionally; the flight plan could/should have been cross referenced. We did speak up and ask for confirmation; at which time ATC just cleared us to a new fix.I will be more diligent in the future.
Original NASA ASRS Text
Title: B737 flight crew reported a heading deviation due to similar fix names.
Narrative: I was Captain and the PM (Pilot Monitoring) on this leg. SEA was a mess due to a closed runway and taxiways. We paid particular attention to the taxi out and it went perfect. We took off 34C flying the SUMMA1 Departure. Passing Summa Seattle Center cleared us to direct to KOTAA. I typed in KOTTA and went to 'PLAN' mode and had FO (First Officer) (PF [Pilot Flying]) 'verify'; which he did. I executed it and selected LNAV. We were basically heading straight to KOTTA. ATC queried us as to our heading and then cleared us to our filed route. We proceeded [to the route] and completed the flight.Event occurred because I typed in the incorrect fix and we both believed it was correct. The two fixes are KOTAA (correct fix for us) and KOTTA (incorrect fix for us but close enough to be confusing). I should have had the IFR page up with our route and all waypoints selected and cross referenced it. Additionally; the flight plan could/should have been cross referenced. We did speak up and ask for confirmation; at which time ATC just cleared us to a new fix.I will be more diligent in the future.
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.