FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03LA186 · S. FL. Ultralights, Inc. Capella Classic

19 Sept 2003 · Port Charlotte, FL, United States

S. FL. Ultralights, Inc. Capella Classic · Accident: total loss of engine power (non-mechanical) en route

From Punta Gorda Airport (KPGD) to Punta Gorda Airport (KPGD)

Report a problem

Event

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

S. FL. Ultralights, Inc. Capella Classic

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
N82536
Operator
Unknown
Onboard fatalities
Unknown
Route
From Punta Gorda Airport (KPGD), Punta Gorda, FLTo Punta Gorda Airport (KPGD), Punta Gorda, 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
En route · cruise
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
Total loss of engine power (non-mechanical)
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

  • Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, encountered
  • Reason for occurrence undetermined

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 that he preflighted the airplane which included checking the fuel tanks for contaminants; none were reported. He then started the engine and taxied the airplane to a fixed base operator (FBO) were 5 gallons of 100 low lead fuel were added to each wing fuel tank which already contained about 3-4 gallons of automotive fuel. After fueling, he again checked the fuel tanks for contaminants; none were found. He started the engine, taxied to the runway, and performed an engine run-up before departure, no discrepancies were noted. He applied power, climbed to 20 feet above ground level, then landed on the remaining portion of the runway; there was no problem with the engine or airplane that caused him to land. He elected to depart from the same runway, and applied power from the spot where the airplane had been stopped from the previous landing. After takeoff, the flight remained in the traffic pattern where he performed two touch-and-go landings. After takeoff from the second, the flight proceeded away from the airport and approximately 20 minutes later when flying at 1,000 feet, the engine rpm dropped from 4,900 to 1,900. Attempts to restore engine power by cycling each fuel selector valve which had been in the "on" position, pumping the throttle, and checking the magnetos were unsuccessful in restoring engine power. He maneuvered the airplane for a forced landing which occurred in a vacant lot. After touchdown, the airplane cart wheeled coming to rest upright in a shallow retention pond with the fuselage resting on the right wing, and a section of the left wing separated. Initial examination of the engine at the accident site by an FAA airworthiness inspector revealed no fuel at the mechanical fuel pump. Additionally, he did not smell fuel at the scene. The airplane was recovered for further examination. Examination of the engine by a representative of the engine manufacturer and a FAA airworthiness inspector approximately 1 week after the accident revealed the gascolator was found to contain fluid contaminated with water. Examination of the carburetor bowls revealed evidence of long term contamination by dirty fuel and water beading. The fuel slides of each carburetor was noted to be installed incorrectly related to indexing the slide to the throttle bore. Examination of the oil system revealed no evidence of oil starvation. Impact damage was noted to the propeller. At a later date the engine was installed on a test stand and impact damaged components necessary for the attempted engine run were replaced. The engine was started and operated to 90 percent rated power with crushed exhaust pipes and no engine coolant. A noticeable vibration was noted during the engine run.

Probable cause

The loss of engine power for undetermined reasons and the unsuitable terrain encountered by the pilot during the forced landing resulting in the airplane cart wheeling and subsequent substantial damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03LA186
Event ID
20030925X01593
Case number
MIA03LA186
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: e57a4540b8408d43e647eec11602b75b9fbbffe0cdef350c867f422d94e8ebaa; retrieved 2026-09-21T19:21:46.442Z.