MIA01LA078 · Learjet 35A
Learjet 35A · Accident: hard landing
From Miami International Airport (MIA) to Punta Gorda Airport (PGD)
Event
- NTSB case
- MIA01LA078
- 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
- Instrument Meteorological Cond
Learjet 35A
- Aircraft type
- Learjet 35
- 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
- N394JP
- Operator
- Pervez Khan
- Onboard fatalities
- Unknown
- Route
- From Miami International Airport (MIA), Miami, FLTo Punta Gorda Airport (PGD), 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
- Landing
- 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
- Hard landing
- 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, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane landed hard on runway 03, blew out the left main landing gear tires and traveled about 4,100 feet down the runway before coming to a stop. According to the pilot he radioed ATC that he had the airport and runway in sight. At 800 feet he lost sight of the runway because of "light fog." He performed a missed approach and stayed in the pattern VFR. On the second approach he was distracted by the fog, but said he did not lose sight of the runway. He said that the co-pilot advised him to go around again but he landed. He said the landing was hard, but did not realize he had a problem until the airplane started pulling to the left. When the airplane came to a stop he got everyone out because of a fuel leak. The 30-minute CVR recording was found to have no data that could contribute to determining the probable cause, and no transcript was prepared. The reported visibility at the time of the accident was 0.25 sm mile with fog. The pilot called the Saint Petersburg flight service station about 2 hours after the accident to report same.
Probable cause
the pilot misjudged the flare resulting in a hard landing, and impact with the runway. A factor in the accident was reduced visibility because of ground fog.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01LA078
- Event ID
- 20010221X00477
- Case number
- MIA01LA078
- 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: e34634446373567261551e3ca113e2fcce6ce0cd8706f2c2b804270f75f14ecf; retrieved 2026-09-22T12:09:49.792Z.