FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA210 · Cirrus Design Corp. SR-22

18 Jun 2005 · Phoenix, AZ, United States

Cirrus Design Corp. SR-22 · Accident: in flight collision with terrain/water on approach

From Stellar Airpark (P19) to Casa Grande Municipal Airport (CGZ)

Report a problem

Event

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

Cirrus Design Corp. SR-22

Aircraft type
Cirrus SR-22
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
N626Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Stellar Airpark (P19), Chandler, AZTo Casa Grande Municipal Airport (CGZ), Casa Grande, 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
Approach · VFR go-around
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 terrain/water
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 › Go-around, delayed
  • Pilot in command › Raising of flaps, not performed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted terrain about 50 yards from the runway during an attempted go-around from a practice power off forced landing. The airplane was in cruise at 5,500 feet when the pilot decided to do a practice emergency power off landing to an airport below him. He set up for left traffic to runway 21. The rpm was idling between 800-1,000 rpm and he was maintaining 85-88 knots air speed. He set the flaps to 50 percent about 800 feet above ground level (agl). The airplane was descending through 450 feet agl when he decided that he was too low to make the runway and he initiated a go-around. He added power, and did not bring the flaps up. He pulled the stick back and established a positive pitch up attitude. He thought that the engine responded, but the airplane was still descending and it impacted terrain about 50 yards from the airport. During a post accident examination, the engine ran successfully through the range of power settings from idle up to 2,600 rpm. The engine ran for approximately 3 minutes. Downloaded information from the Avidyne Engine Data Log indicated that during the last 6 seconds of recorded data, the rpm went from 1,200 to a maximum of 2,300, manifold pressure went from 8.8 to 21.4 inches, and fuel flow went from 1.9 to 19.2. The recorded data did not show any anomalies in power development for the flight.

Probable cause

the pilot's delay in executing a timely go-around and failure to raise the flaps, which resulted in a collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA210
Event ID
20050705X00931
Case number
LAX05LA210
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: e79df005a4916dff0ffe60a8ba172b8c653672aa18f2e435d3b95289aff2c150; retrieved 2026-09-22T05:46:17.733Z.