ERA09LA469 · Raytheon Aircraft Company 58
Quest Diagnostics Raytheon Aircraft Company 58 · Accident: landing area overshoot
From Heritage Field (PTW) to Teterboro Airport (TEB)
Event
- NTSB case
- ERA09LA469
- 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
- 1 · 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
- Visual Meteorological Cond
Raytheon Aircraft Company 58
- Aircraft type
- Beechcraft 58
- 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
- N167TB
- Operator
- Quest Diagnostics
- Onboard fatalities
- Unknown
- Route
- From Heritage Field (PTW), Pottstown, PATo Teterboro Airport (TEB), 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 · flare/touchdown
- 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
- Landing area overshoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft propeller/rotor
- 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 airplane was operating as a corporate flight transporting medical specimens on a night, visual approach in visual meteorological conditions when the accident occurred. The flight was scheduled to be a single-pilot operation conducted under the provisions of 14 Code of Federal Regulations Part 91, and the pilot-in-command (PIC) had been assigned to the flight. Although the second-in-command (SIC), also a Quest Diagnostics pilot, was not assigned to the flight, he asked the PIC if he could accompany him on the flight to gain familiarization with operations into Teterboro Airport. Typically, the PIC flies the airplane from the left seat; however, the PIC on this flight allowed the SIC to occupy the left seat and fly the airplane. The investigation could not determine if the pilots had coordinated responsibilities for the flight before departure or if the PIC was providing additional training to the SIC during the flight.
Radar data indicated that, while on the base leg of the traffic pattern, the airplane had an airspeed of about 204 knots, which exceeded the maximum flap extension speed by more than 50 knots and the maximum landing gear extension speed by more than 80 knots. According to the SIC, during this critical portion of the approach to landing, the nonflying PIC remained focused on providing familiarization of the airport and city environment to the SIC, who was flying the airplane, and the PIC failed to monitor the airplane’s airspeed. After the SIC recognized the airplane’s excessive approach speed close to the runway environment, he attempted to slow the airplane. However, he inadvertently retarded the propeller levers and feathered the propellers instead of retarding the throttle levers. Recognizing the resultant loss of thrust, the PIC challenged the SIC’s actions and stated that both engines had experienced power loss. The airplane’s unfeathering accumulators had been removed; therefore, it was not possible for either pilot to quickly unfeather the propellers and reestablish engine power. Approaching the runway centerline at both low altitude and high airspeed and with the propellers feathered, the pilots were unable to slow the airplane and descend before overflying the runway. The airplane crossed the runway threshold at 300 feet and 186 knots (90 knots more than the approach speed of 96 knots), departed airport property, struck objects, and burst into flames.
Chairman Hersman and Member Rosekind did not approve this brief. Chairman Hersman filed a dissenting statement, which Member Rosekind joined. Member Rosekind filed a dissenting statement, which Chairman Hersman joined. Member Sumwalt filed a concurring statement, which Vice Chairman Hart and Member Weener joined. The statements can be found in the public docket for this accident.
Probable cause
The complete loss of thrust due to the second-in-command’s (SIC) inadvertent feathering of both propellers during a high-speed, low-altitude approach. Contributing to the accident was the pilot-in-command’s inadequate monitoring of the SIC’s performance.
Chairman Hersman and Member Rosekind did not approve this probable cause. Chairman Hersman filed a dissenting statement, which Member Rosekind joined. Member Rosekind filed a dissenting statement, which Chairman Hersman joined. Member Sumwalt filed a concurring statement, which Vice Chairman Hart and Member Weener joined. The statements can be found in the public docket for this accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09LA469
- Event ID
- 20090821X62833
- Case number
- ERA09LA469
- 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: 08c80dcb237434c20d0c87904009de733e6b2be0a1c82564bab103a70f3462f0; retrieved 2026-09-13T20:26:09.737Z.