FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89LA138 · Cessna 150M

28 Mar 1989 · Mesa, AZ, United States

Cessna 150M · Accident: in flight collision with object while maneuvering

From Falcon Field (FFZ) to an unrecorded destination

Report a problem

Event

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

Cessna 150M

Aircraft type
Cessna 150
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
N7592U
Operator
Tidd, Robert L · private individual
Onboard fatalities
Unknown
Route
From Falcon Field (FFZ), Mesa, 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
Maneuvering
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
In flight collision with object
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
Wire, transmission
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 › Proper altitude, not maintained
  • Pilot in command › Visual lookout, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE STUDENT PLT RPRTD THAT DURING FLT, SOMETHING SUDDENLY SMASHED THE WINDSHIELD. HE SAID HE TEMPORARILY LOST CONTROL OF THE ACFT, THEN REGAINED IT AT LOW ALTITUDE. HE WAS HAVING TROUBLE MAINTAINING ALTITUDE & OPTED TO MAKE AN EMERGENCY LANDING IN A PICNIC AREA. DURING THE LANDING, THE ACFT COLLIDED WITH A TREE & A FENCE POST. AN INSPN OF THE ACFT REVEALED NO EVIDENCE OF A BIRD STRIKE. HOWEVER, THERE WAS AN INDENTATION THAT RAN ALONE THE LEADING EDGE OF THE LEFT WIND & ACROSS THE WINDSHIELD. THERE WAS NO RPRTD TRANSMISSION WIRE DAMAGE, BUT WITNESSES IN THE AREA RPRTD SEEING AN ACFT FLYING AT LOW LEVEL.

Probable cause

INADEQUATE VISUAL LOOKOUT BY THE PILOT, AND HIS FAILURE TO MAINTAIN THE PROPER ALTITUDE. FACTORS RELATED TO THE ACCIDENT WERE: THE PILOT'S LACK OF VISUAL PERCEPTION AT DUSK, THE TRANSMISSION LINE, AND THE OBSTRUCTIONS (TREE & FENCE) IN THE EMERGENCY LANDING AREA.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX89LA138
Event ID
20001213X27927
Case number
LAX89LA138
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1989-03-29.
  • API snapshot SHA-256: 51dee75a42bb6d63e28c3129b303abe41cca2d9ff1ac6a53eb45e82f77ba1af3; retrieved 2026-09-22T00:15:39.324Z.