FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX88FA204 · Taylorcraft BL65

30 May 1988 · Eloy, AZ, United States

Taylorcraft BL65 · Accident: loss of control in flight en route

From Eloy Municipal Airport (E60) to an unrecorded destination

Report a problem

Event

NTSB case
LAX88FA204
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
2 · 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

Taylorcraft BL65

Aircraft type
Taylorcraft BL65
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
N27463
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eloy Municipal Airport (E60), Eloy, AZTo 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
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 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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Remedial action, not performed
  • Pilot in command › Stall, inadvertent

Approximate · Estimated position: the centre of Eloy, AZ, the place the record names. Not the accident site.

NTSB narrative

SHORTLY AFTER TAKEOFF, DURING TAKEOFF CLIMB, AIRCRAFT WAS OBSERVED OUT OF CONTROL SPIRALLING TO GROUND. PILOT HAD RESTORED THE AIRCRAFT AND HAD ONLY 12 HOURS OF FLIGHT EXPERIENCE IN MAKE AND MODEL. PILOT HAD FAILED HIS FIRST FLIGHT TEST FOR PRIVATE PILOT RATING 17 MONTHS PRIOR TO ACCIDENT. IMPROPER USE OF FLIGHT CONTROLS DURING STALL RECOVERY WAS CITED IN NOTICE OF DISAPPROVAL. THERE WAS NO RECORD OF PILOT RECEIVING FORMAL TRAINING IN ACCIDENT AIRCRAFT MAKE AND MODEL.

Probable cause

FAILURE OF THE PILOT TO MAINTAIN CONTROL OF THE AIRCRAFT DURING TAKEOFF CLIMB RESULTING IN AN INADVERTENT SPIRAL. CONTRIBUTING TO THIS ACCIDENT WAS THE PILOT'S LACK OF TOTAL EXPERIENCE IN THE AIRCRAFT MAKE AND MODEL.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX88FA204
Event ID
20001213X25719
Case number
LAX88FA204
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: 0ea56fe84489e472f273a0305fb2ac312eabb0a2b1b92bf38163c732a7a2fbd4; retrieved 2026-09-21T03:42:11.232Z.