FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09FA437 · Cessna 152

9 Sept 2009 · Coolidge, AZ, United States

Air Safety Flight Academy Cessna 152 and Oxford Airline Training Center Piper PA-28-161 · Accident: midair collision en route

Report a problem

Event

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

Aircraft 1 · 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
N94741
Onboard fatalities
Unknown
Route
From Coolidge Municipal Airport (P08), Coolidge, AZTo Glendale Municipal Airport (KGEU), Glendale, AZ
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
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
Midair collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Piper PA-28-161

Aircraft type
Piper PA-28
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
N994T
Onboard fatalities
Unknown
Route
From KCZG · Casa Grande, AZTo Phoenix Goodyear Airport (KGYR), Goodyear, AZ
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
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
Midair collision
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 › Psychological

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

NTSB narrative

Both airplanes involved in the mid-air collision were on simulated instrument meteorological conditions training flights in visual flight rules conditions. Both lesson profiles called for the pilot in the left-seat to wear a vision-restricting instrument training hood, while the pilot in the right seat acted as a safety/lookout pilot. The airplanes were being operated in an area of high density student training. The left seat pilot of the Piper had just rolled out of a right turn associated with the entry to a practice holding pattern to a non-controlled airport. The left-seat pilot of the Cessna had departed a non-controlled airport and was in an en route climb to the cruise altitude, at which he would return to his home airport. Neither airplane was receiving radar traffic advisories, nor was either in contact with a controlling Federal Aviation Administration (FAA) facility. The pilots in the Piper said that they were monitoring the designated practice area frequency, and had heard no other airplanes in the immediate area. The survivor in the Cessna could not clearly remember if he had been making position calls on the practice area frequency, but his radio was found set to that frequency and he said that he had been trained to make such calls. The Cessna was on a magnetic ground track of about 265 degrees, and the Piper had rolled out on a course intercept heading of 288 degrees about 10 to 15 seconds prior to the collision. The collision took place at 4,500 feet. During the collision sequence, the Cessna's right wing penetrated the lower left engine cowl of the Piper, and the Piper's left main landing gear wheel and tire impacted the right side of the Cessna's aft fuselage. After the impact, during which a portion of the Cessna's right wing and tail section separated, the Cessna entered an uncontrolled descent into the terrain and the pilots in the Piper executed a power-off forced landing. The weather at the time was reported as clear skies with 10 miles visibility. Neither safety/lookout pilot saw the other airplane prior to the collision.

Probable cause

The failure of both safety/spotter pilots to see and avoid the other airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09FA437
Event ID
20090909X44833
Case number
WPR09FA437
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. 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: ff5b0dd0e095fe30b1104655db7194ad5dad4c1b7750080bb4c20dbb46098d71; retrieved 2026-09-13T18:04:52.592Z.