FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA173 · Great Lakes 2T-1A-2

14 May 2005 · Sonoma, CA, United States

Great Lakes 2T-1A-2 · Accident: partial loss of engine power (mechanical failure) during initial climb

From Sonoma Valley Airport (0Q3) to an unrecorded destination

Report a problem

Event

NTSB case
LAX05LA173
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
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
Visual Meteorological Cond

Great Lakes 2T-1A-2

Aircraft type
Great Lakes 2
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
N765GL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sonoma Valley Airport (0Q3), Sonoma, CATo not recorded
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
Initial climb
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
Partial loss of engine power (mechanical failure)
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

  • Fuel injection control/system › Excessive flow/output
  • Fuel system, fuel control › Leak

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 collided with the runway during an aborted takeoff following a partial loss of engine power. Prior to departure the pilot completed an engine run-up, observing no anomalies with the engine gauges or the engine's performance. During the takeoff, as the pilot began to lift off of the runway surface, the engine began to surge and he noticed a subsequent degradation in climb performance. After reaching about 30 to 40 feet above ground level (agl), he realized the airplane would not be able to continue the departure and opted to perform an emergency landing on an alternate runway. The airplane collided with the runway in a 15-degree nose low attitude. A post accident examination of the engine found that the spark plugs, the cylinders, and piston heads were heavily sooted; signatures consistent with an excessively rich fuel mixture. No other anomalies were found that would have precluded the engine from normal operation. An examination of the fuel servo revealed that the unit had a black coloration in the throat section and blue staining present near the idle valve. These signatures were consistent with a rich fuel mixture and a continuous fuel leak. During the bench testing of the servo, several small fuel leaks were noted at the idle valve, fuel diaphragm, and center body seal. Flow tests at high power settings revealed that the fuel servo was running rich, well over the prescribed maximum flows for that unit. The unit was about 28 years old and did not appear to have ever been overhauled. A representative from the engine manufacturer stated that based on the fuel servo's tested flow, the engine would have been running very rich and most likely could not have produced normal power. The servo manufacturer issued a Service Bulletin in 1990 that recommends that the unit be overhauled at engine TBO or every 10 years.

Probable cause

a partial loss of engine power, which resulted from the fuel servo leaking and generating an excessively rich fuel/air mixture. A factor was the owner's failure to comply with a service bulletin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA173
Event ID
20050525X00668
Case number
LAX05LA173
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: 10979312ac7a84b1b07c03ecb3d337f2fb9f71daff18606ea8a82fec700c4f6d; retrieved 2026-09-21T19:01:41.956Z.