ERA09CA505 · Quicksilver Sport 2S
Quicksilver Sport 2S · Accident: loss of engine power (total) during initial climb
From Southerland Strip (FD92) to Southerland Strip (FD92)
Event
- NTSB case
- ERA09CA505
- 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
Quicksilver Sport 2S
- Aircraft type
- Quicksilver SPORT 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
- N781PJ
- Operator
- Petrus C. Leenen · private individual
- Onboard fatalities
- Unknown
- Route
- From Southerland Strip (FD92), Geneva, FLTo Southerland Strip (FD92), Geneva, FL
- 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 engine power (total)
- 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 power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated he performed a routine pre-flight inspection and engine start, followed by a normal pre-takeoff checklist, including a magneto check. The takeoff and initial climb were uneventful; however, approximately 250 feet above ground level, the “engine quit abruptly; there was no sputtering.” The pilot maintained control and the airplane subsequently landed in high grass, which resulted in substantial damage to the airframe. He reported about 165 hours of total flight experience, which included about 93 hours in make and model. Postaccident examination by a Federal Aviation Administration inspector and a mechanic revealed an air bubble in the oil line and a scored piston, indicating that a lack of lubricating oil caused the piston to seize during operation. Prior to the accident flight, the pilot reported that he removed the oil filter, inspected it for contaminants, and reinstalled the same filter. According to the pilot, the engine was new in 2004 and had approximately 299 hours time in service.
Probable cause
Oil starvation due to air in the engine oil supply line, which resulted in engine seizure during initial climb.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA505
- Event ID
- 20090908X35512
- Case number
- ERA09CA505
- 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: 6124c7ce26447ca78e1c69b87991779f8b3a7d2c69ca2459530b5051a7c5de97; retrieved 2026-09-15T12:55:07.049Z.