FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC03FA173 · Learjet 35A

4 Aug 2003 · Groton, CT, United States

Learjet 35A · Accident: loss of control in flight while maneuvering

From Republic Airport (FRG) to Groton New London Airport (GON)

Report a problem

Event

NTSB case
NYC03FA173
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
2 · 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

Learjet 35A

Aircraft type
Learjet 35
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
N135PT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Republic Airport (FRG), Farmingdale, NYTo Groton New London Airport (GON), Groton, CT
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
Maneuvering
First occurrenceThe 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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Copilot/second pilot › Raising of flaps, inadvertent
  • Pilot in command › Low altitude flight/maneuver, performed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

About 5 miles west of the airport, the flightcrew advised the approach controller that they had visual contact with the airport, canceled their IFR clearance, and proceeded under visual flight rules. A witness heard the airplane approach from the east, and observed the airplane at a height consistent with the approach minimums for the VOR approach. The airplane continued over the runway, and entered a "tight" downwind. The witness lost visual contact with the airplane due to it "skimming" into or behind clouds. The airplane reappeared from the clouds at an altitude of about 200 feet above the ground on a base leg. As it overshot the extended centerline for the runway, the bank angle increased to about 90-degrees. The airplane then descended out of view. The witness described the weather to the north and northeast of the airport, as poor visibility with "scuddy" clouds. According to CVR and FDR data, about 1.5 miles from the runway with the first officer at the controls, and south of the extended runway centerline, the airplane turned left, and then back toward the right. During that portion of the flight, the first officer stated, "what happens if we break out, pray tell." The captain replied, "uh, I don't see it on the left side it's gonna be a problem." When the airplane was about 1/8-mile south of the runway threshold, the first officer relinquished the controls to the captain. The captain then made an approximate 60-degree heading change to the right back toward the runway. The airplane crossed over the runway at an altitude of 200 feet, and began a left turn towards the center of the airport. During the turn, the first officer set the flaps to 20 degrees. The airplane reentered a left downwind, about 1,100 feet south of the runway, at an altitude of 400 feet. As the airplane turned onto the base leg, the captain called for "flaps twenty," and the first officer replied, "flaps twenty coming in." The CVR recorded the sound of a click, followed by the sound of a trim-in-motion clicker. The trim-in-motion audio clicker system would not sound if the flaps were positioned beyond 3 degrees. About 31 seconds later, the CVR recorded a sound similar to a stick pusher stall warning tone. The airplane impacted a rooftop of a residential home about 1/4-mile northeast of the approach end of the runway, struck trees, a second residential home, a second line of trees, a third residential home, and came to rest in a river. Examination of the wreckage revealed the captain's airspeed indicator reference bug was set to 144 knots, and the first officer's was set to 124 knots. The flap selector switch was observed in the "UP" position. A review of the Airplane Flight Manual revealed the stall speeds for flap positions of 0 and 8 degrees, and a bank angle of 60 degrees, were 164 and 148 knots respectfully. There were no charts available to calculate stall speeds for level coordinated turns in excess of 60 degrees. The flightcrew was trained to apply procedures set forth by the airplane's Technical Manual, which stated, "…The PF (Pilot Flying) will call for flap and gear extension and retraction. The PNF (Pilot not flying) will normally actuate the landing gear. The PNF will respond by checking appropriate airspeed, repeating the flap or gear setting called for, and placing the lever in the requested position... The PNF should always verify that the requested setting is reasonable and appropriate for the phase of flighty and speed/weight combination."

Probable cause

The first officer's inadvertent retraction of the flaps during the low altitude maneuvering, which resulted in the inadvertent stall and subsequent in-flight collision with a residential home. Factors in the accident were the captain's decision to perform a low altitude maneuver using excessive bank angle, the flight crews inadequate coordination, and low clouds surrounding the airport.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC03FA173
Event ID
20030814X01339
Case number
NYC03FA173
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 476c4d95df14387cf91b0c08a76944d683eaeb853fdaab64d0d0153d2b06ebdb; retrieved 2026-09-20T19:00:50.431Z.