FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13FA118 · Cessna 152

8 Feb 2013 · Tucson, AZ, United States

Arizona Aero-Tech Cessna 152 · Accident before flight

From Tucson International Airport (TUS) to Ryan Field (RYN)

Report a problem

Event

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

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
N89059
Onboard fatalities
Unknown
Route
From Tucson International Airport (TUS), Tucson, AZTo Ryan Field (RYN), Tucson, AZ
Aircraft age
About 34 years (built 1979)
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
Prior to flight
Defining eventThe 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
Miscellaneous/other
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

  • Personnel issues › Physical

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot rented the airplane from the fixed-base operator (FBO) to fly to an airport about 11 miles away to practice takeoff and landings. He spoke briefly with two people in the FBO office and then went out to the airplane to preflight it and have it fueled. Review of the departure airport air traffic control tower (ATCT) communications and air traffic control radar tracking data did not reveal any abnormalities with the departure or flight. About 7 minutes after departure, the pilot contacted the ATCT at his destination airport and advised the controller that he was planning to do three touch-and-go maneuvers. Per instructions from the controller, the pilot entered a right downwind for his assigned landing runway. When the airplane was near a location consistent with it being established on the base leg, several motorists observed it in a steep nose-down attitude and descending rapidly. The airplane impacted flat terrain about 1.5 miles from the airport. Neither of the two ATCT controllers observed the descent or impact. Examination of the airframe and engine did not reveal any preimpact anomalies that would have precluded continued engine operation or flight.

The pilot had obtained his first Federal Aviation Administration (FAA) medical certificate about 10 years before the accident, received annual recertification, and his most recent medical certificate was issued about 13 months before the accident. Review of the pilot's FAA medical records indicated that, for the intervening 9 years, the pilot was being treated for multiple cardiac issues and was subject to repetitive specialized medical testing. Further review indicated that the pilot had slow, essentially asymptomatic, progression of at least two components of his cardiac disease that are both independently associated with a significantly increased risk of sudden cardiac death as a result of a sudden arrhythmia. Although autopsy results indicated that the cause of death was blunt trauma, it is likely that a complication of the pilot's cardiac disease caused him to become incapacitated, which resulted in his loss of control of the airplane and the subsequent crash. The 0707 code found on the transponder was likely an artifact of the pilot's attempt to switch to the 7700 emergency code to indicate a problem to the controllers, but neither the timing nor the underlying reason for that action could be determined.

Probable cause

The pilot's incapacitation due to his preexisting cardiac disease, which resulted in his degraded or complete loss of ability to control the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13FA118
Event ID
20130208X43909
Case number
WPR13FA118
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: f01d0cbddf174a4dc113208223728e9f9ae0eedefc8f9517ded81d3e23d6989a; retrieved 2026-09-14T15:52:39.841Z.