ATL04LA199 · Adventura II
Adventura II · Accident: loss of engine power en route
From Naples Municipal Airport (KAPF) to Naples Municipal Airport (KAPF)
Event
- NTSB case
- ATL04LA199
- 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
Adventura II
- Aircraft type
- Adventura II
- 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
- UNREG
- Operator
- Roger Borg
- Onboard fatalities
- Unknown
- Route
- From Naples Municipal Airport (KAPF), Naples, FLTo Naples Municipal Airport (KAPF), Naples, 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 · climb to 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
- Loss of engine power
- 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 › Flare, improper
- 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 completed one high speed taxi on runway 23, and then started a second high speed taxi at which time he attempted to take off. The pilot applied full power and climbed to approximately 100 feet. As he continued the climb, he noticed the airplane was not performing properly. The passenger stated she heard the airplane engine surging. The pilot reported the engine problem to the control tower and his last transmission stated "I need to make a 180 and come back". The 180-degree turn was never completed and the airplane landed hard at the end of runway 23. The flight was never cleared for takeoff. Examination of the airplane revealed the main landing gear collapsed, the aluminum support tubes fractured, and the float attachment tube fractured.
Probable cause
Loss of engine power for undetermined reasons and the pilot's improper landing flare which resulted in a hard landing and collapse of the main landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA199
- Event ID
- 20041203X01908
- Case number
- ATL04LA199
- 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: 7bc99667fdb064a1baea96dc809a76d48f5f728fd8f605aec025312ed92de75f; retrieved 2026-09-21T19:11:58.609Z.