MIA96LA004 · Louks PULSAR XP
Louks PULSAR XP · Accident: loss of control in flight during takeoff
From X40 to an unrecorded destination
Event
- NTSB case
- MIA96LA004
- 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
- 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
Louks PULSAR XP
- Aircraft type
- Louks 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
- N912XL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From X40To not recorded
- 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
- Takeoff
- 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 control in flight
- 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
- Stall/mush
- 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 › Rotation, premature
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he performed an engine run-up before departure with no discrepancies noted. He initiated a takeoff in a no-wind condition with the flaps retracted. The pilot stated that after lift-off, he leveled off about 4 to 5 feet above the runway to build airspeed. He stated that the 'plane dropped, left wing more that right, aircraft skidded off runway, and hit runway marker along edge of runway at approximately 10 mph.' A postcrash fire erupted in the right wing area after the airplane came to rest. Both occupants were seriously burned. The passenger died later due to burns. The pilot stated that there was no preimpact failure or malfunction of the engine or flight control.
Probable cause
Premature rotation by the pilot during takeoff, which resulted in an inadvertent stall/mush, while attempting to accelerate in ground effect after lift-off.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96LA004
- Event ID
- 20001207X04752
- Case number
- MIA96LA004
- 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: 98e18cdaa5c0dc1160f268489ddadb4fbea7bcb81b02fdf4deb5e34d6ec3e717; retrieved 2026-09-20T23:34:17.634Z.