FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15FA277 · Cirrus Design Corp SR20

22 Jul 2015 · Lake Wales, FL, United States

Cirrus Design Corp SR20 · Accident: loss of control in flight on approach

From Orlando Sanford International Airport (SFB) to Page Field (FMY)

Report a problem

Event

NTSB case
ERA15FA277
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

Cirrus Design Corp SR20

Aircraft type
Cirrus SR20
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
N610DA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Orlando Sanford International Airport (SFB), Sanford, FLTo Page Field (FMY), Fort Myers, FL
Aircraft age
About 8 years (built 2007)
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
Approach · VFR go-around
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
Destroyed

Cause areas

  • Aircraft › Aircraft power plant
  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor reported that, during an instructional flight and while demonstrating how to change the route in the GPS, he noticed a "puff" of black smoke appear from under the legs of the pilot receiving instruction. The smoke dissipated quickly, and seconds later, the oil pressure light illuminated, accompanied by an aural warning. The flight instructor took control of the airplane and declared an emergency before diverting to a nearby airport. The flight instructor stated that, while on short final approach for landing, he thought "he was too high and going too fast to make the runway." He could not slow the airplane sufficiently for a safe landing and decided to conduct a go-around; however, when he advanced the throttle, the engine did not respond. When the airplane was about 400 ft above ground level, he instructed the pilot receiving instruction to activate the airframe parachute; however, the parachute did not arrest the descent before the airplane crashed in wooded terrain. The flight instructor was seriously injured, and the pilot receiving instruction was fatally injured.

Postaccident examination of the engine revealed that the oil control rings on all the pistons were stuck. The oil ports on the pistons were clogged, and coking was present. The Nos. 1 through 3 connecting rod bearings showed evidence of the beginning stages of oil starvation. Review of the maintenance logbooks Revealed that during the two months preceding the accident, engine oil consumption increased significantly. It is likely that the engine consumed more oil in the month before the accident due to the stuck oil control rings, which caused the engine case to pressurize and vent oil overboard via the breather tube, consistent with the large amount of oil residue noted on the underside of the fuselage during the wreckage examination. The vented oil also likely resulted in the "puff" of smoke that the instructor saw during the flight. Data downloaded from the airplane's multifunction displays revealed that the oil pressure decreased significantly but that engine power was still available before the accident, indicating that, although the flight instructor stated that the engine did not respond to his throttle input, the engine was operating and producing some power at the time of the accident.

Although the manufacturer did not specify a minimum or maximum altitude for deployment of the airframe parachute, manufacturer-published information indicated that the demonstrated altitude loss from a straight-and-level deployment was 400 ft. The actual altitude loss during any deployment depended upon the airplane's attitude, altitude, speed, and other environmental factors. The Pilot's Operating Handbook stated that airframe parachute deployment at high speed, low altitude, or in high wind conditions could result in severe injury or death to the aircraft occupants.

Probable cause

A partial loss of engine power due to oil starvation. Contributing was the flight instructor's failure to maintain control of the airplane during an aborted emergency landing, and his delayed decision to deploy the airplane's parachute system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15FA277
Event ID
20150722X35237
Case number
ERA15FA277
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: 59be55d7cda45d920dad7b611819ed10f766d71df1dc3f15eedbad41dc1cf29e; retrieved 2026-09-14T19:46:18.661Z.