FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Comair Flight 5645

21 Jul 2004 · Snow Hill, VA, United States

Bombardier CL-600 · Accident while maneuvering

From Charleston International Airport (CHS) to John F. Kennedy International Airport (JFK)

Report a problem

Event

NTSB case
NYC04LA174
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
Accident
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 CL-600

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
N995CA
Operator
Comair
Onboard fatalities
Unknown
Route
From Charleston International Airport (CHS), Charleston, SCTo John F. Kennedy International Airport (JFK), NEW YORK, NY
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
Maneuvering
First occurrenceThe 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

  • Pilot in command › Maneuver, excessive

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight crew received a traffic advisory (TA) alert from the Traffic Alert and Collision Avoidance System (TCAS), followed shortly by an aural resolution advisory (RA) warning to "CLIMB, CLIMB." The first officer (FO) then disconnected the autopilot and initiated a climb, at a rate of ascent of 1,500 feet per minute. The captain then announced he was taking the controls and proceeded to pitch the airplane at a greater angle. As the airplane ascended, the flight attendant fell to the floor and broke her ankle. Once the TCAS announced, "clear of conflict," the captain leveled the airplane at 30,000 feet. He then returned the controls to the FO, and the airplane was descended back to an assigned altitude of FL 290. A review of radar data and air traffic control information, revealed that the accident airplane was climbing at a rate of 2,500 feet per minute and an airspeed of 483 knots. The airplane which caused the traffic alert for the accident airplane was an MD-80, which was climbing at 2,000 feet per minute, and an airspeed of 433 knots. The closest proximity between the two aircraft was 1.54 nautical miles, and 1,500 feet. According to the operator's Flight Standards Manual, "the correct response to a corrective RA is to fly from the red zone into the green zone. This maneuver requires a response within 5 seconds of the advisory using approximately a 0.25g maneuver". A performance review of the radar data revealed the flight crew's maneuver in response to the TCAS alert included a 1,000-foot climb, followed immediately by a descent back to the airplane’s assigned altitude. The maneuver described by the radar data could be performed using an initial 1.15 G pull-up to start the climb, followed by a 0.05 push-over to arrest the climb and start the descent, followed by a 1.4 G pull-up to level the airplane at the assigned altitude. In this sequence, the time between the 0.05 G push-over and the 1.4 G level-off was about 5 seconds.

Probable cause

The pilot's excessive maneuvering in response to a TCAS alert, which resulted in a serious injury to the flight attendant.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04LA174
Event ID
20040812X01200
Case number
NYC04LA174
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, coordinates, 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: ab920a9abc00ae3cb8ed1a340eb7983122657b381350e0464bc8785fe438e59d; retrieved 2026-09-18T15:21:12.104Z.
  • The NTSB's operator name is blank for N995CA; the operator shown is the name the NTSB records it doing business as.