FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX03LA055 · Lipscomb Lancair 235

28 Dec 2002 · Payson, AZ, United States

Lipscomb Lancair 235 · Accident: loss of control in flight during landing

From Payson Airport (PAN) to Pattani Airport (PAN)

Report a problem

Event

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

Lipscomb Lancair 235

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
N777KL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Payson Airport (PAN), PAYSON, AZTo Pattani Airport (PAN)
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 · aborted
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/spin
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 › Airspeed, not maintained

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 stalled during an aborted landing, entered a spin, and impacted the ground. Multiple pilot witnesses stated that the airplane made two approaches that culminated in go-arounds. On the third approach, the airplane landed hard about 1,500 feet down the runway. The airplane bounced into the air, landed back on the runway, bounced up once more, and then they heard the engine power up to abort the landing. The airplane climbed to about 100 feet and the witnesses saw the airplane's nose pitch up and the angle of attack continue to increase as the airplane flew down the runway at a slow airspeed. The left wing dropped, the airplane rotated into a spin, and then it impacted the ground. An inspection of the airplane revealed no mechanical anomalies. The pilot purchased the accident airplane 2 days prior to the accident. A review of the pilot's medical application indicated that he had not flown in the last 6 months. A review of his logbooks revealed that the pilot had no flight time in the accident airplane make and model. The broker who sold him the airplane, asked the pilot to fly with someone that was familiar with the accident airplane make and model before flying it solo. The day of the accident, the pilot informed the broker that he wanted to taxi test it. On the second high-speed taxi test, the airplane became airborne. The broker attempted to contact the pilot after the airplane departed the airport environment. The airplane returned about an hour later, and flew two circuits around the airport below traffic pattern altitude. It was on the third approach that the airplane landed hard, bounced into the air, and climbed to an altitude of about 150 feet in a wings level attitude, before the pilot lost control of it.

Probable cause

the pilot's failure to maintain an adequate airspeed during an aborted landing that resulted in an inadvertent stall/spin. A contributing factor in the accident was the pilot's lack of familiarity with the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX03LA055
Event ID
20030103X00009
Case number
LAX03LA055
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: 41be0eb4015b7db0ea71df86732ebd1446ced1feca600bb15338f1db9ffc84df; retrieved 2026-09-20T19:32:28.562Z.