British Aerospace BAE-125-700A incident near Teterboro, New Jersey, March 9, 2005
On March 9, 2005 at about 2:50 am local time, a British Aerospace BAE-125-700A, registered N703TS, suffered minor damage in an incident near Teterboro, New Jersey (Teterboro Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot in command's inadequate in-flight planning, which resulted in an overrun landing on a contaminated runway. Factors were inadequate crew coordination, gusty winds, and a slush covered runway.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 9, 2005 · about 2:50 am local time
- Place
- Teterboro, New Jersey · Teterboro Airport · map
- Type
- Incident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- British Aerospace BAE-125-700A · all BAE-125-700As on the register
- Registration
- N703TS · no longer on the register · serial 257031
- Damage
- Minor damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
Prior to the day of the incident, the pilot and copilot had not flown together. In addition, the copilot spoke broken English. The copilot obtained the current ATIS information about 150 miles from the airport. Although the ATIS information reported thin slush on all surfaces, the captain had not asked about runway conditions, and the copilot did not relay the information regarding runway conditions. The flightcrew continued the approach in moderate to severe turbulence, and performed pre-landing checks. Due to the turbulence, the flightcrew missed several radio transmissions, including the aircraft ahead them that reported a go-around, and later reported good braking action. The incident airplane turned onto final approach for runway 01; a 7,000-foot-long, 150-foot-wide, asphalt runway. During the final approach, the landing gear was down and flaps were in the 25-degree extended position. Air Traffic Control (ATC) relayed the good braking action report to the incident flightcrew, based upon the previous arrival aircraft. However, the previous arrival aircraft was equipped with thrust reversers, and the incident airplane was not. ATC also provided two wind checks to the incident airplane while on final approach. The wind checks were reported as 340 degrees at 15 knots, and 340 degrees at 20 knots, respectively. The pilot reported that due to the wind, he flew the final approach without full flaps, at Vref plus 20 (139 knots), and slowed to 134 knots over the runway threshold. According to the Aeronautical Information Manual Pilot/Controller Glossary, a contaminated runway, "is considered contaminated whenever standing water, ice, snow, slush, frost in any form, heavy rubber or other substances are present." Review of an "Effect of Slippery Runway on Landing Distance" chart, available in the FAA approved airplane flight manual, revealed that the "equivalent scheduled landing distance available," for the contaminated 7,000-foot-long runway, was approximately 3,200 feet. Review of a takeoff and landing data (TOLD) card retrieved from the cockpit revealed that a landing weight of 20,000 pounds, with full flaps extended, at 119 knots, required 4,240 feet of runway for landing. That data assumed a dry runway.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
- Flight time: 9,000 hours in all; 350 in this make and model; 350 in the last 90 days; 100 in the last 30 days; 5,000 as pilot in command; 0 on instruments
- Last flight review: December 1, 2004
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Co-pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: helicopter
- Flight time: 11,352 hours in all; 1,350 in this make and model; 16 in the last 90 days; 0 in the last 30 days; 10,252 as pilot in command; 0 on instruments
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 9,380 hours
- Last inspection: continuous airworthiness programme, February 1, 2005; 10 hours since
- Maximum gross weight: 25,000 lb
- Seats: 11
- Landing gear: retractable
- Engine 1: Garrett TFE731-3R-1h (turbofan); 0 hours total
- Engine 2: Garrett TFE731-3R-1h (turbofan); 0 hours total
The flight
- Departed from: CMH Columbus OH at 2:00 am
- Destination: TEB Teterboro NJ
- Flight plan: IFR
- Runway 1, 7,000 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: night
- Wind: from 320° at 12 knots, gusting 28
- Visibility: 10 statute miles
- Sky: broken clouds at 11,000 ft
- Temperature: 19°F (-7°C), dew point 3°F (-16°C)
- Altimeter: 29.37 inHg
- Observation at 2:51 am from TEB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 2 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
