NTSB CAROL · Event
Event NYC04IA054
Aircraft involved
Probable cause & findings
The captain's inadequate preflight planning, which resulted in an overrun during an aborted takeoff.
Factual narrative
On December 16, 2003, about 1710 eastern standard time, a Canadair CL-600, N95EB, sustained minor damaged during an overrun at Teterboro Airport (TEB), Teterboro, New Jersey. The two certificated airline transport pilots and unknown number of passengers were not injured. Visual meteorological conditions prevailed for the planned flight to McCarran International Airport, Las Vegas, Nevada. An instrument flight rules flight plan was filed for the commercial flight conducted under 14 CFR Part 91. During the morning hours of December 16, another flightcrew had performed a successful aborted takeoff at TEB. The aborted takeoff was completed in the same airplane, on runway 19; a 7,000-foot long, 150-foot wide, asphalt runway. The captain of that flight stated that he made two attempts to rotate the airplane at 132 knots, but there was no response. The captain aborted the takeoff about 139 knots. The captain further stated that he had flown the same airplane for 4 days prior to the aborted takeoff, and did not experience any problems. The most recent flight was the evening prior to the aborted takeoff, in which the captain flew the airplane from Atlantic City, New Jersey, to TEB. The captain added that the aborted takeoff, and the prior flight, were both conducted as demonstration flights for prospective aircraft buyers. He estimated seven to nine passengers were on each flight, but did not know the exact number as different people were boarding and exiting the airplane at different airports. The captain noted that the only difference between the flight from Atlantic City, and the aborted takeoff at TEB, was the addition of 3,000 to 4,000 pounds of fuel at TEB. The captain stated that before and after the aborted takeoff, he computed a weight and balance using an estimated nine passengers. Both computations resulted in the weight and balance being within the limitations of the airplane. However, when asked to produce the calculations, the captain stated that he did not retain them. After the aborted takeoff, the flightcrew was released for the day, and the airplane underwent a maintenance inspection. The maintenance inspection did not reveal any discrepancies pertaining to inability to rotate the airplane, and the airplane was returned to service later that day. The incident flightcrew was then called for the evening trip, and the incident captain was advised of the earlier aborted takeoff. The incident captain reported that he initiated a takeoff on runway 24; a 6,013-foot long, 150-foot wide, asphalt runway. During the takeoff roll, he was unable to rotate the airplane, and aborted the takeoff. The airplane subsequently traveled approximately 75 feet beyond the end of the runway, and came to rest in mud. After a written request, the incident captain failed to provide a copy or recreation of a weight and balance calculation, or the exact number of passengers on board. When asked why he attempted the takeoff on the shorter runway, the incident captain stated that it was the runway in use at the time. After a written request to the first officer, his attorney reported that the captain completed the weight and balance calculations, and there were six passengers on board. Following the incident takeoff, the airplane underwent a maintenance inspection by the aircraft manufacturer, under the supervision of Federal Aviation Administration inspectors. The inspection did not reveal any discrepancies pertaining to the inability to rotate the airplane. Subsequently, on February 25, 2004, the airplane departed TEB and flew to uneventfully to Windsor Locks, Connecticut. There were no passengers on that flight. The airplane manufacturer computed two weight and balance calculations for the incident takeoff. The first calculation assumed two pilots and six passengers, with 15,070 pounds of fuel. The second calculation assumed two pilots and nine passengers, with 15,070 pounds of fuel. Both calculations revealed the airplane was above the maximum gross takeoff weight, and outside the forward center-of-gravity envelope. A representative from the airplane manufacturer stated that the accelerate stop distance for the airplane was factored into the takeoff distance chart in the airplane flight manual (AFM), and the value was less than the published takeoff distance. Review of a takeoff distance chart for the make and model airplane revealed: at 41 degrees F, at maximum gross weight, with no wind or runway gradient, the airplane would require approximately 5,500 feet of runway for takeoff. The reported weather at TEB, at 1651, was: wind variable at 4 knots; visibility 8 miles; few clouds at 6,000 feet; temperature 41 degrees F; dew point 32 degrees F; altimeter 30.11 inches Hg. Earlier in the day, a different flightcrew performed a successful aborted takeoff in the incident airplane. The aborted takeoff occurred with seven to nine passengers on board, at 139 knots; when the flightcrew was unable to rotate the airplane. The only difference between that aborted takeoff, and the uneventful previous flight, was the addition of 3,000 to 4,000 pounds of fuel. Following that aborted takeoff, the airplane underwent a maintenance inspection which did not reveal any discrepancies pertaining to the inability to rotate. The airplane was then returned to service. When the incident captain arrived at the airport, he was informed of the previous aborted takeoff. The incident captain attempted a takeoff on a shorter runway at the airport. During rotation, the airplane did not respond to elevator inputs, and the captain aborted the takeoff. The airplane then traveled off the end of the runway and came to rest in mud. Following the overrun, the incident captain failed to produce a weight and balance calculation, or accurate count of passengers on board at the time. The wind was reported as variable at 4 knots. When asked why he chose a shorter runway to attempt the takeoff, the incident captain reported that it was the runway in use at the time. The aircraft manufacturer inspected the airplane, and did not find any discrepancies pertaining to the aborted takeoff. The manufacturer also computed two weight and balance calculations for the incident takeoff. Both calculations revealed that the airplane was above the maximum gross takeoff weight, and outside the forward center-of-gravity envelope. Subsequently, the airplane tookoff with no passengers on board, and flew uneventfully to another airport. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_NYC04IA054.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 (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗