FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Northwest Airlines Flight 188

21 Oct 2009 · Minnesota, United States

Airbus A320 212 · Pilot error and distraction

From San Diego International Airport (SAN) to Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP)

Report a problem

Event

NTSB case
DCA10IA001
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
Occupants
149
Survivors
149
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Airbus A320 212

Aircraft type
Airbus A320
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N374NW
Onboard fatalities
Unknown
Route
From San Diego International Airport (SAN), San Diego, CATo Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MN
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Air traffic event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

From the Wikipedia article

Northwest Airlines Flight 188 was a regularly scheduled flight from San Diego, California, to Minneapolis–Saint Paul, Minnesota, on October 21, 2009, which overshot its destination by more than 150 mi because of pilot error. During the event, air traffic control lost contact with the flight for approximately 75 minutes. The flight later landed at Minneapolis–Saint Paul International Airport over an hour past its scheduled arrival.

As a result of the incident, the Federal Aviation Administration (FAA) revoked the pilot certificates of the involved pilots and the National Transportation Safety Board (NTSB) issued recommendations for changes to air traffic control procedures and the rules for cockpit crew. The incident also caused American lawmakers to move to prevent pilots on U.S. airliners from using personal electronic devices while taxiing or flying.

Incident

The Airbus A320 took off from San Diego International Airport at 5:01 p.m. CDT (3:01 pm in San Diego). It was scheduled to land at 8:01 p.m. CDT. Just under two hours after takeoff, at 6:56 p.m. CDT, Air Traffic Control lost radio contact with the aircraft while it was over Denver.

During the flight, Denver ARTCC (where contact was lost) instructed the pilots to contact the Minneapolis ARTCC as the aircraft was leaving Denver's airspace. However, the pilots did not do so. Both the Denver and Minneapolis ARTCC made several unsuccessful attempts to reach the pilots. At the request of the Minneapolis ARTCC, Northwest's dispatchers made at least eight attempts to reach the pilots and urge them to reestablish radio contact, without success. When other pilots in the area got word of the situation, they tried to help the controllers, attempting to reach the pilots as well. Northwest also sent them a text message through ACARS, which went unanswered. Authorities were concerned enough that NORAD readied fighter jets to check on the welfare of the plane. Officials at the White House Situation Room were alerted as well.

Just as the fighter jets were about to scramble, air traffic control at Minneapolis-St. Paul International Airport reestablished radio contact with the plane at 8:14 p.m. CDT, by which time the flight was over Eau Claire, Wisconsin, roughly 100 mi east of Minneapolis. Captain Timothy Cheney and first officer Richard Cole said that they were not aware of their location until a flight attendant asked them what time they were due to land. The overshoot concerned air traffic controllers enough that they had the pilots perform a series of maneuvers to confirm the pilots were in control of the plane, as well as to verify that the transponder target they were receiving on their radar was indeed Flight 188. The aircraft finally landed, over an hour late, at 9:04 p.m. CDT.

Investigation and cause

Investigation

During the investigation, Cheney and Cole told the National Transportation Safety Board investigators that they were going over schedules using their laptop computers—a serious breach of piloting fundamentals, as well as a violation of Delta Air Lines policy (Delta had recently merged with Northwest). The pilots denied suggestions from some aviation safety experts that they had fallen asleep. The cockpit voice recorder retains only the last 30 minutes of audio after being powered off and thus audio recordings were not available for the complete duration of the flight's loss of radio contact.

Findings

On October 27, 2009, the FAA revoked the certificates of both pilots. The incident and subsequent investigation have led to changes in the rules for cockpit crew and air traffic controllers. One issue of particular concern was the delay, exceeding an hour, from the time air traffic controllers realized the plane was out radio contact until an alert on the Domestic Events Network (DEN) was created and NORAD was informed of the situation. The commander of NORAD, General Gene Renuart Jr., said in an interview that ideally an alert is created within 10 minutes of losing contact and if they had been alerted in time, fighter jets would have been scrambled to intercept. An updated FAA notice effective November 10, 2010, called for an alert to be made within five minutes of last recorded radio contact.

Text from the Wikipedia article “Northwest Airlines Flight 188” (revision 1363361814, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

PILOTS

While Northwest Airlines flight 188 (NWA188) was in cruise flight at 37,000 feet, air traffic control (ATC) directed the flight crew to change radio frequency as the airplane approached one of the sectors in Denver ATC airspace. The first officer acknowledged the frequency change and read back the correct frequency of 132.17 megahertz (MHz). However, the flight crew did not contact ATC on the new frequency. Further, there was no radio microphone keying recorded on the flight data recorder, indicating that the crew made no attempted radio transmissions on any frequency until they transmitted on 132.125 MHz, which was the frequency for Winnipeg ATC. Winnipeg ATC directed the flight crew to contact Minneapolis ATC; the flight was operating with no radio communications (NORDO) for about 1 hour 17 minutes. Because of the proximity of the Winnipeg ATC frequency (132.125 MHz) to the last frequency acknowledged by the pilots (132.17 MHz), it is likely that the first officer began to dial in the new frequency but never completed the frequency change. (To make a frequency change, the pilot had to use a rotary dial to select the desired frequency and then push a button to activate the new frequency on the radio.) Furthermore, the first officer did not attempt to contact the next ATC controller after acknowledging the frequency change. The first officer stated that the last contact with ATC was shortly before they had dinner. Thus, the first officer was likely directed to change frequencies about the time that the captain was absent from the cockpit (due to a restroom break) and the flight attendant was in the cockpit (in compliance with security procedures), which coincided with the time dinner was served. These events may have distracted the first officer from completing the frequency change or attempting to contact the next ATC controller. Additionally, the captain’s temporary absence from the cockpit would have removed the redundant monitoring of a second pilot who may have detected the incomplete frequency change or failure to check in with ATC.

Following the captain’s return to the cockpit, the pilots became distracted by a conversation regarding changes to the bidding process (the process by which the pilots request their flight schedule for the following month) resulting from the merger between NWA and Delta. The pilots allowed this conversation to monopolize their attention and, thus, lower their capacity to monitor their radio communications, notice the lack of contact, and recognize, via airplane instruments, the flight’s progress. Both pilots stated that they heard radio chatter but did not hear a radio call for NWA188. During the pilots’ conversation, the pilots opened and operated their personal laptop computers. Postincident investigation revealed that laptops could block the pilots’ primary flight and navigation displays depending on their placement, but would most likely not block the upper screen of the electronic centralized aircraft monitor, where “ACARS [aircraft communication addressing and reporting system] MSG” blinks. The computers not only restricted the pilots’ direct visual scan of all cockpit instruments but also further focused their attention on non-operational issues, contributing to a reduction in their monitoring activities, loss of situational awareness, and lack of awareness of the passage of time. The pilots missed numerous visual alerts, including ACARS messages sent by NWA dispatch (ACARS does not have an aural alert) and at least nine messages regarding their position (on the multifunction control and display unit and the primary flight displays) as they neared Minneapolis-St Paul International/Wold-Chamberlain Airport without landing data entered into the flight management computer. Airline policy in effect at the time of the incident prohibited the use of portable electronic devices on the flight deck.

Although the pilots indicated that they had one of their radios tuned to 121.5 MHz (the universal emergency frequency), they did not respond to calls from ATC on that frequency. It could not be determined why the pilots did not respond. Possible reasons include: the volume was turned down; the pilots were distracted; or the airplane was outside of coverage for the 121.5 MHz transmitters.

ATC

NWA188 entered the first two Denver ATC sectors uneventfully; as the airplane entered the next two sectors, radio contact was not established. The controllers were preparing for a shift change, and neither sector controller’s relief briefing included information that communication had not been established with the NWA188. Although the current ATC practice of using automated information transfers (electronic radar handoffs) in some sectors provides an efficient means for tracking and handing off airplanes between controllers, there are no system-wide procedures for indicating that an aircraft has been directed to switch frequencies or has communicated with ATC. Because of this lack of standardization, NWA188 passed through two Denver ATC sectors without the controllers being aware that it had not made radio contact. When the flight was finally identified as NORDO by the next sector’s controller, almost 30 minutes after NWA188’s last transmission, controllers attempted to regain contact with the airplane by calling NWA dispatch personnel and requesting that they attempt to contact NWA188. The controllers indicated during interviews that this technique is commonly used initially for air carrier airplanes instead of transmitting on the universal emergency frequency of 121.5 MHz because of the limited range of sparsely located transmitters. However, when the pilots did not respond to the ACARS messages, one of the controllers made several attempts to contact the airplane on 121.5 MHz, but the pilots did not respond.

FAA Order 7110.65, Air Traffic Control Handbook, Paragraph 10-4-4. Communications Failures states, in part, the following.

Take the following actions, as appropriate, if two-way radio communications are lost with an aircraft. ... a. In the event of lost communications with an aircraft under your control jurisdiction use all appropriate means available to reestablish communications with the aircraft. These may include, but not be limited to, emergency frequencies, NAVAIDs [navigation aids] that are equipped with voice capability, FSS [flight service station], Aeronautical Radio Incorporated (ARINC), etc. ... e. If radio communications have not been (re)established with the aircraft after five minutes, consider the aircraft's activity to be possibly suspicious and handle the flight per FAAO JO 7610.4, Chapter 7, Hijacked/Suspicious Aircraft Reporting and Procedures.

Controllers and supervisors interviewed after this incident indicated that an air carrier airplane out of radio contact is not an uncommon occurrence for air traffic controllers, occasionally occurring as often as several times during an 8-hour shift. However, these interviews indicated that the losses of radio contact are usually short in duration and re-established quickly. This likely contributed to the controllers becoming complacent and not advising ATC managers of the loss of radio contact with NWA188 in a timely manner. In this incident, during which the airplane was NORDO for more than 1 hour, failure to quickly advise managers resulted in a delay in the completion of necessary actions and notifications required by the lost-communications procedures.

The NTSB makes the following conclusions regarding this incident. • The first officer acknowledged but never completed the assigned frequency change due to interruptions, likely during the time that the captain was absent from the cockpit and the flight attendant was in the cockpit. • Not completing the frequency change, contacting ATC, and maintaining communications was contrary to Federal Aviation Regulations and airline procedures and was not noticed by the flight crew because they became distracted by a conversation, during which they referenced their personal computers, focusing the pilots’ attention on non-operational issues. • The pilots’ conversation and use of personal computers led to reduced monitoring activities, loss of situational awareness, and lack of awareness of the passage of time. • Sufficient visual cues, including ACARS messages and flight progress alerts, were presented to the flight crew, but the crew did not notice any of them. • Air traffic controllers did not follow procedures to ensure NWA188 was on the correct frequency, which delayed the identification of NWA188 as NORDO. • No national standardized procedures exist when automated information transfers are used instead of the paper flight progress strips to nonverbally document and confirm air traffic control information among controllers. • ATC management did not complete the required notifications for a NORDO airplane in a timely manner as required by Federal Aviation Administration directives.

Probable cause

The flight crew's failure to monitor the airplane’s radio and instruments and the progress of the flight after becoming distracted by conversations and activities unrelated to the operation of the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

Wikipedia article: Northwest Airlines Flight 188
Article
Northwest Airlines Flight 188
Revision
1363361814 · 2026-07-09 · retrieved 2026-09-18
Wikidata
Q16958964
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA10IA001
Event ID
20091022X00120
Case number
DCA10IA001
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "Northwest Airlines Flight 188" (page 42038313, revision 1363361814); merged with NTSB case DCA10IA001 (events / aircraft)
Date
NTSB record DCA10IA001: NTSB narrative opening date, consistent with the API date and time (local date)
Place and country
Wikipedia infobox: site; country from NTSB record DCA10IA001
Map position
NTSB record DCA10IA001: events decimal coordinates
Aircraft, operator and route
NTSB record DCA10IA001: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record DCA10IA001: operated under Part 121: Air Carrier
Fatalities
NTSB record DCA10IA001: NTSB API totalFatal
Ground fatalities
NTSB record DCA10IA001: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "Northwest Airlines Flight 188" and NTSB case DCA10IA001, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.