MIA98LA224 · Lesemann PULSAR XP
Lesemann PULSAR XP · Accident: loss of engine power on approach
From Leonard M. Thompson International Airport (MYAM) to Treasure Coast International Airport (FPR)
Event
- NTSB case
- MIA98LA224
- 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
- 0
- 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
Lesemann PULSAR XP
- Aircraft type
- Lesemann PULSAR XP
- 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
- N701JL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Leonard M. Thompson International Airport (MYAM), MARSH HARBORTo Treasure Coast International Airport (FPR), 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
- Approach
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation; Wire, static
- 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 › Fuel management, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed on a VFR cross-country flight. While on approach at the destination airport, the airplane experienced a total loss of engine power. The pilot switched the fuel selector valve from its original position at takeoff to the opposite tank, and attempted an engine restart with negative results. He maneuvered the airplane to avoid a collision with high voltage lines, and to line up with a road that he selected as a forced landing area. The left wing collided with a tree, the airplane continued forward, and collided with an electrical line. The nose of the airplane pitched down, and the airplane collided with the terrain and nosed over inverted. Postcrash examination revealed fuel in the left tank and no fuel in the right tank.
Probable cause
The pilot's improper fuel management during a cross country flight which resulted in a total loss of engine power during the approach for landing and subsequent in-flight collision with wires and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA98LA224
- Event ID
- 20001211X10920
- Case number
- MIA98LA224
- 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. 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: e290d74db46d2a1a9e5bfa767f8ae11f1e02a47ad1b7ea2a3420dad55e84d87f; retrieved 2026-09-21T20:43:20.555Z.