FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07CA103 · Cessna 152

17 Apr 2007 · Oak Glen, CA, United States

M.Y. Air Cessna 152 · Accident: in flight collision with object while maneuvering

From L12 · Redlands, CA to L12

Report a problem

Event

NTSB case
SEA07CA103
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
Visual Meteorological Cond

Cessna 152

Aircraft type
Cessna 152
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
N49902
Operator
My Air
Onboard fatalities
Unknown
Route
From L12 · Redlands, CATo L12
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
Tree(s)
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(cfi) › Altitude/clearance, 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 flight instructor said that he had the student under the hood and was giving him headings to follow. He said that as they approached the mountains the aircraft began to lose altitude. The flight instructor said that he took control of the airplane and attempted to maneuver the airplane out of the downdraft. He said that even with full power, the aircraft settled and impacted a tree. He said the airplane "spun around 180 degrees and landed in a small stream [approximately 2 inches deep] on its landing gear." The flight instructor said that the airplane was destroyed.

Probable cause

The flight instructors failure to maintain clearance from trees while maneuvering. Contributing factors were the downdraft weather condition, and the tree.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07CA103
Event ID
20070525X00642
Case number
SEA07CA103
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: 550aa4491f8bb78104a396a6fbb83e7217f7224da81d2e9b3e74c0f823c18659; retrieved 2026-09-21T18:32:35.053Z.