FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Mesa Airlines Bombardier, Inc. CL-600 2B19 incident

13 Feb 2008 · Hilo, HI, United States

Bombardier, Inc. CL-600 2B19 · Incident en route

From Daniel K. Inouye International Airport (HNL) to HTO · Hilo, HI

Report a problem

Event

NTSB case
SEA08IA080
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
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
Visual Meteorological Cond

Bombardier, Inc. CL-600 2B19

Aircraft type
Bombardier CL-600
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
N651BR
Onboard fatalities
Unknown
Route
From Daniel K. Inouye International Airport (HNL), Honolulu, HITo HTO · Hilo, HI
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 · climb to cruise
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
Miscellaneous/other
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 › Physical

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

NTSB narrative

go! flight 1002 departed for its destination about 0916 Hawaii standard time. About 0930, the captain transmitted to air traffic control (ATC) that the flight was climbing through 11,700 feet to its cruise altitude of flight level (FL) 210 (approximately 21,000 feet mean sea level.) The controller acknowledged the transmission and cleared the flight to proceed to an intersection along the flight route located about 29 miles north-northwest of the destination airport, and the flight crew acknowledged. At 0933, during cruise flight, the controller repeated the navigational clearance, which the flight crew acknowledged, and the airplane turned in accordance with the clearance. At 0940, the controller instructed the flight to change radio frequencies, and there was no response. The controller continued to try to contact the flight crew multiple times but received no reply. At 0951, the airplane crossed the intersection that was its clearance limit then turned southeast toward the destination airport without descending, which is consistent with the airplane being on autopilot. The controller handling the flight asked another controller to attempt to contact the flight crew on a different frequency, but there was still no response, and the flight proceeded on a southeasterly heading at FL 210. About 0955, the flight crossed over the destination airport and continued on a southeasterly course without changing altitude or heading. Two separate airline crews in the area attempted to contact the incident crew, but neither flight crews’ attempts were successful.

About 0958, when the flight was about 26 nautical miles southeast of the destination airport, the captain contacted the controller with an abbreviated call sign (“Ah HCF ten zero two”), and the controller asked if the flight crew was experiencing an emergency. The captain responded, "No, we must have missed a hand off or missed a call or something." The controller then issued instructions for the flight to return to the destination airport, with which the flight crew complied. The flight arrived without further incident about 1015.

The captain and first officer both reported to their company that they had unintentionally fallen asleep in flight. The fact that both pilots fell asleep during the midmorning hours, a time of day normally associated with wakefulness and rising alertness, indicates that both pilots were fatigued.

The captain had undiagnosed severe obstructive sleep apnea, which was diagnosed during a medical evaluation shortly after this incident and for which symptoms (such as snoring) and risk factors (such as obesity) were present before the incident. This condition likely caused him to experience chronic daytime fatigue and contributed to his falling asleep during the incident flight.

In addition, the day of the incident was the third consecutive day that both pilots started duty at 0540. This likely caused the pilots to receive less daily sleep than is needed to sustain optimal alertness and resulted in an accumulation of sleep debt and increased levels of daytime fatigue. The first officer stated he needed between 7.5 and 8 hours of sleep per night to feel rested. He estimated that he had spent about 7 hours 25 minutes in bed the night before the incident, and about 6 hours 55 minutes in bed during each of the previous two nights. Thus, the first officer’s self-reported sleep history indicated an accumulated sleep debt of between 1 hour 15 minutes and 2 hours 45 minutes in the 72 hours before the incident. The first officer’s reduced sleep probably resulted from the flight crew’s recent work schedule. The effect of early start times on sleep is well documented. A 1998 National Aeronautics and Space Administration Report, “Flight Crew Fatigue II: Short-haul fixed wing air transport operations,” for example, concluded that requiring early report times makes it more difficult for crewmembers to obtain adequate sleep. Further, a 1998 report published by North Atlantic Treaty Organization Research and Technology Organization (formerly AGARD), “Early starts: Effects on sleep, alertness, and vigilance,” concluded that pilots reporting before 0600 had a significantly shorter total sleep time, impaired sleep quality, and impaired performance both pre-flight and at top of descent. The pilots also were flying eight legs a day, requiring many takeoffs and landings, which are high-workload phases of flight.

The incident pilots’ lack of adequate sleep, together with the low workload associated with the cruise phase of the flight, likely contributed to the pilots inadvertently falling asleep.

Probable cause

The captain and first officer inadvertently falling asleep during the cruise phase of flight. Contributing to the incident were the captain's undiagnosed obstructive sleep apnea and the flight crew’s recent work schedules, which included several consecutive days of early-morning start times.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08IA080
Event ID
20080222X00229
Case number
SEA08IA080
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • 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.
  • API snapshot SHA-256: b0b23f49a1d8108951d3338d9b70321962dec298cd7d9a0760d0bb4d22dbddbd; retrieved 2026-09-15T09:23:04.380Z.