ERA10FA161 · Cessna T303
Cessna T303 · Accident: loss of control in flight during initial climb
From Louisa County Airport / Freeman Field (LKU) to Danville Regional Airport (DAN)
Event
- NTSB case
- ERA10FA161
- 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
Cessna T303
- Aircraft type
- Cessna 303
- 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
- N9305T
- Operator
- James A Youngquist · private individual
- Onboard fatalities
- Unknown
- Route
- From Louisa County Airport / Freeman Field (LKU), Louisa, VATo Danville Regional Airport (DAN), Danville, VA
- 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
- 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
- Loss of control in flight
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During takeoff, one witness noted that at least one engine seemed to be running rough and not making power. Several other witnesses, located about 1/2 mile northwest of the airport, observed the accident airplane pass overhead in a right turn. They reported that the engine noise did not sound normal. Two of the witnesses noted grayish black smoke emanating from the airplane. The airplane then rolled left and descended nose down into the front yard of a residence. Review of maintenance records revealed the airplane underwent an annual inspection and extensive maintenance about 3 months prior to the accident. One of the maintenance issues was to troubleshoot the right engine that was reportedly running rough at cruise. During the maintenance, the right engine fuel pump, metering valve, and fuel manifold were removed and replaced with overhauled units. Additionally, the right engine fuel flow was reset contrary to procedures contained in an engine manufacturer service information directive; however, the fuel pump could not be tested due to thermal damage and the investigation could not determine if the fuel flow setting procedure contributed to the loss of power on the right engine. On-scene examination of the wreckage and teardown examination of both engines did not reveal any preimpact mechanical malfunctions. Teardown examination of the right propeller revealed that the blades were not at or near the feather position, which was contrary to the emergency procedure published by the manufacturer, to secure the engine and feather the propeller in the event of an engine power loss. The right propeller exhibited signatures consistent with low or no power at impact, while the left propeller exhibited signatures consistent of being operated with power at impact.
Probable cause
The pilot's failure to maintain aircraft control and secure the right engine during a loss of engine power after takeoff. Contributing to the accident was the loss of engine power on the right engine for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10FA161
- Event ID
- 20100304X35234
- Case number
- ERA10FA161
- 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. 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: fe8cb157da03a7ab18cf46d8a59b25d174e503f395f5cbe3e3aece86a496979f; retrieved 2026-09-13T20:41:03.897Z.