LAX07FA062 · Cirrus Design Corp. SR22
Cirrus Design Corp. SR22 · Accident: in flight collision with terrain/water en route
From Winslow Lindbergh Regional Airport (INW) to Henderson Executive Airport (HND)
Event
- NTSB case
- LAX07FA062
- 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
- Instrument Meteorological Cond
Cirrus Design Corp. SR22
- Aircraft type
- Cirrus SR22
- 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
- N457S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Winslow Lindbergh Regional Airport (INW), Winslow, AZTo Henderson Executive Airport (HND), Las Vegas, NV
- 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 · cruise
- 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
- Destroyed
Cause areas
- Pilot in command › 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
During the pilot's initial flight home, she encountered weather and decided to land at an intermediate airport. While on the ground she was in communication with her spouse who was providing her with weather updates from the local area FAA flight service station (FSS). They both decided that she would stay the night and he would drive out and pick her up. About an hour later, she and her husband decided that it would be okay for her to continue her flight home if she took an alternate route that would take her south, away from the encroaching weather. Once she found better weather in a southerly direction she would then continue her flight to the west to her intended destination. The pilot reported to her husband that she would file a flight plan in the air; however, there was no record of one being filed. Her husband notified the FAA when the pilot did not arrive at her destination airport. Search and rescue personnel located the wreckage 5 days after the accident in a mountainous canyon area. The airplane came to rest on the side of a canyon wall oriented in an uphill direction, after it had clipped several trees. The accident site was about 200 feet below a mesa, at an elevation of 4,600 feet. Investigators located all of the major components of the airplane and noted that the CAPS system (Cirrus Airframe Parachute System) had deployed due to impact forces, and was lying next to the airplane in the debris field. The airframe and engine inspections revealed no mechanical anomalies that would have precluded normal operations. There were no radio communications received by any air traffic control facilities from the pilot during the accident flight. The weather in the area at the time of the accident showed that the cloud bases were near 6,000 feet with the cloud tops above 15,000 feet. Visibilities were between 0 miles in the clouds and 3 miles below the clouds, with a freezing level near 6,500 feet. Another pilot flying northeast of the accident site reported moderate rime and mixed icing conditions from 8,500 feet to 16,000 feet. Recorded weather briefings between the FAA FSS and the pilot's spouse indicated that he received all the pertinent weather information for the flight. The spouse relayed that he told her there were no buildups for a flight to the southeast. An in-flight weather advisory for AIRMET Zulu Update 4 for icing issued by the National Weather Service for the time of the accident reported moderate icing between 9,000 feet to 18,000 feet. The freezing level was forecasted to be between 4,000 and 8,000 feet. The FAA approved airplane flight manual contains several locations where it indicates that flight into known icing is prohibited. According to astronomical data from the US Naval Observatory, sunset on December 18th occurred at 1724 MST, and the moon was below the horizon.
Probable cause
The pilot's failure to maintain terrain clearance during cruise flight while flying at night at an altitude to remain clear of clouds and icing conditions. Contributing to the accident were an inadequate weather evaluation, the clouds, icing conditions, and the dark night lighting conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07FA062
- Event ID
- 20070109X00028
- Case number
- LAX07FA062
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-12-19.
- API snapshot SHA-256: 99b0173158983d39365ac383ed7df968debb2c0ad0fb2db37ed966fb2a4e8d68; retrieved 2026-09-20T16:57:23.373Z.