NTSB CAROL · Event
Event NYC04LA174
Registry · N995CA
FAA Aircraft Registry record.
Make / Model
COSTRUZIONI AERONAUTICHE TECNA P2012 TRAVELLER
Year of manufacture
2020
TCDS
A00076CE · COSTRUZIONI AERONAUTICHE TECNAM S P A
Engine
LYCOMING TEO-540-C1A (375 hp)
Seats / Engines
11 seats · 2 engines
Last airworthiness date
20210217
ADS-B equipped
Yes — Mode-S ADE569
Registrant of record
HYANNIS AIR SERVICE INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's excessive maneuvering in response to a TCAS alert, which resulted in a serious injury to the flight attendant.
Factual narrative
On July 21, 2004, at 0815 eastern daylight time, a Bombardier CL-600, N995CA, operated by Comair Airlines Inc., as flight 5645, was not damaged during a climb to avoid traffic near Snow Hill, Virginia. The two certificated airline transport pilots, and two non-revenue passengers were not injured. One flight attendant was seriously inured. Visual meteorological conditions prevailed for the flight that departed from the Charleston International Airport (CHS), Charleston, South Carolina, destined for the John F. Kennedy International Airport (JFK), New York, New York. An instrument flight rules flight plan was filed for the scheduled passenger flight conducted under 14 CFR Part 121. According to the first officer (FO), while in cruise flight at flight level (FL) 290, the crew received an audible traffic advisory (TA) alert from the traffic collision avoidance system (TCAS). The multi-functional display depicted an aircraft at the 12-to 1-o'clock position, about 2,000 feet below, and climbing about 500 feet per minute. As the conflicting aircraft reached approximately 1,400 feet below the CL-600, the first officer visually observed the airplane, announced "traffic in sight, " and alerted the captain to the traffic. At the same time as the captain instructed the FO to climb, the crew received an aural resolution advisory (RA) warning to "CLIMB, CLIMB" from the TCAS. The FO then disconnected the autopilot and initiated a climb, while advancing the thrust levers. The captain continued his instruction to climb and the vertical speed indicator displayed 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. 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 FL 290. After the airplane was level, the captain was informed that the flight attendant was hurt. The flight continued to JFK, where the flight crew requested that paramedics meet the flight to assess the flight attendant's injury. According to the flight attendant, she was performing a walk-through of the cabin, when she "felt pressure on herself, " and fell to the floor. Two jumpseating passengers in the cabin assisted her to a seat, and retrieved ice for her ankle. After landing, she was transported to an urgent care facility, and diagnosed with a broken ankle. A review of radar data and air traffic control information provided by the Federal Aviation Administration (FAA), revealed that the Comair flight 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 Comair crew 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 Comair CL-600 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. Listed below [is one] possible corrective RA aural warning: - 'CLIMB, CLIMB,' - Climb at the rate shown on the VSI, normally 1,500 FPM." A performance review of the radar data revealed the flight crew response to the TCAS alert included a 1000-foot climb, followed immediately by a descent back to the airplane’s assigned altitude. The entire maneuver lasted about a minute and a half. While the nature of the radar data that tracked the flight did not allow the load factors in the cabin to be computed with certainty, 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. According to Comair training documents, flight crews receive initial TCAS training, during simulator LOFTs. During recurrent training, TCAS training/demonstrations may be built into specific LOFT scenarios. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_NYC04LA174.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- arXiv 2024 · arXiv preprint
A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
- arXiv 2022 · arXiv preprint
Experimental Flight Testing of a Fault-Tolerant Adaptive Autopilot for Fixed-Wing Aircraft
This paper presents an adaptive autopilot for fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2021 · arXiv preprint
An Adaptive Digital Autopilot for Fixed-Wing Aircraft with Actuator Faults
This paper develops an adaptive digital autopilot for a fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2020 · arXiv preprint
Reinforcement Learning for Robust Missile Autopilot Design
Designing missiles' autopilot controllers has been a complex task, given the extensive flight envelope and the nonlinear flight dynamics.
Browse the full corpus — academia portal ↗