ERA11IA006 · Gulfstream Aerospace G-IV
Gulfstream Aerospace G-IV · Incident: runway excursion during landing
From Toronto Pearson International Airport (CYYZ) to Teterboro Airport (KTEB)
Event
- NTSB case
- ERA11IA006
- 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
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Gulfstream Aerospace G-IV
- Aircraft type
- Gulfstream G-IV
- 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
- N923CL
- Operator
- Avenue Capital Managment II
- Onboard fatalities
- Unknown
- Route
- From Toronto Pearson International Airport (CYYZ), TorontoTo Teterboro Airport (KTEB), Teterboro, NJ
- 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 91: General Aviation
- 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
- Landing · landing roll
- 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
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot-in-command (PIC) was the pilot flying and the copilot was the pilot monitoring. As the flight approached Teterboro Airport (TEB), Teterboro, New Jersey, the pilots received the current automated terminal information service data, which included visibility 2 miles in light rain and mist, ceiling 800 feet broken, and wind from 360 degrees at 6 knots, gusting to 16 knots. The pilots programmed the flight management system with the current data, which provided a reference speed (ref) of 136 knots. The approach was briefed and the PIC elected to add 10 knots to the Vref speed due to the wind conditions. The flight descended on a localizer approach for runway 6, a 6,013-foot-long, 150-foot wide, grooved asphalt runway. The autopilot was disconnected after the airplane descended through 1,000 feet mean sea level (msl) at Vref plus 10 knots. As the airplane descended through 700 feet msl, the copilot obtained a wind check from the tower controller, which indicated the wind was from 010 degrees at 15 knots, gusting to 25 knots. FDR data indicate that the airspeed slowed from Vref plus 10 knots to Vref, and the PIC disconnected the autothrottles about 645 feet msl, in an attempt to manually control the throttles and regain airspeed. The airspeed then fluctuated from Vref plus 5 knots to Vref plus 15 knots.
The copilot made airspeed callouts throughout the approach, which included Vref plus 15 as the airplane descended through 200 feet and Vref plus 15 again as the airplane was 40 feet above the runway. The airplane descended into ground effect at 150 to 160 knots, floated and bounced, before finally touching down with approximately 2,250 feet of runway remaining (as captured in airport surveillance video). The thrust reversers were timely deployed by the captain and operated correctly. The ground spoilers, brakes, and anti-skid system also operated correctly when automatically deployed; however, the airplane traveled off the end of the runway about 40 to 50 knots and came to rest 100 feet into an engineered materials arresting system. There was no mention of a go-around by either pilot during the flight.
According to the PIC's written statement, the airplane was at Vref speed, just prior to touchdown, when a gust of wind caused it to float. He further stated that at no point did either pilot believe there was not adequate runway remaining to continue the landing. After touchdown, at 80 knots, the PIC and copilot continued to believe the airplane would stop on the remaining runway; however, the airplane had floated about 65 percent of the length of the runway before touching down. During a subsequent telephone interview, the PIC remarked that a Vref plus 15 callout by the copilot, at 50 feet above the runway, would have been cause for an immediate go around; yet neither pilot called for one during the flight. According to the copilot's written statement, it was not apparent to him that the airplane might not stop on the runway until 400 to 500 feet before the end of the runway, when maximum braking and anti-skid were operating.
Data from the airplane manufacturer, for the estimated landing weight, revealed the airplane required a landing distance of approximately 2,820 feet on a dry runway, or 3,600 feet on a wet runway, without wind factored. Runway 1 at TEB is 7,000 feet long but does not have an instrument approach due to the proximity of Newark Liberty International Airport (EWR) airspace (EWR is 10 miles southwest of TEB and has runways in excess of 10,000 feet). The approach to runway 6 has a circling approach to runway 1; however, at the time of the incident, the ceiling was below the circling approach minimums. The pilots could have remained airborne in a holding pattern a few minutes to evaluate whether the ceiling would lift sufficiently to fly the circling approach to the longer runway, they could have diverted to EWR, or they could have initiated a go-around to land on runway 6 when airspeed became excessive. Instead, they continued an unstabilized approach in gusting crosswind conditions and failed to initiate a go around when airspeed at the end of the approach became excessive.
Probable cause
The pilot-in-command's failure to attain the proper touchdown point while landing with a gusting crosswind and failure to initiate a go-around, which resulted in a landing more than halfway down the runway and a subsequent runway overrun. Contributing to the incident was the failure of either pilot to call for a go-around when the airplane was at Vref plus 15 at 50 feet above the runway or once they had floated well beyond the touchdown zone of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11IA006
- Event ID
- 20101004X11133
- Case number
- ERA11IA006
- 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, coordinates. 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: f51f3b2760ea4a4aa7296775458739b9ce46f07b226bb67f0afb418566870639; retrieved 2026-09-15T15:26:55.177Z.