Cessna 172 N7133G
17 April 2016 · Avalon, California, United States · Serious injuries
Summary
On 17 April 2016 at about 23:29 local time, a Cessna 172 registered N7133G was involved in an accident near Avalon, California, United States. 2 people were on board and 2 were seriously injured. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 23:29
- Classification
- Accident
- Location
- Avalon, California, United States
- Nearest airport
- Airport in the Sky (KAVX)
- Coordinates
- 33.4081, -118.4122
- Aircraft
- Cessna 172
- Registration
- N7133G
- Category
- Airplane
- Year built
- 1969
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Long Beach → Avalon
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR16LA093
People
2 people were seriously injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 2 | 0 | 2 | 0 | 0 |
Probable cause
The pilot's failure to maintain a proper approach path on landing because he failed to familiarize himself with the airport's unique approach hazards and recommended procedures before the flight. Also causal was the pilot's failure to recognize the airplane's improper approach and to execute a go-around in a timely manner.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The private pilot and non-pilot rated passenger departed for a personal flight to an island airport located on top of a plateau. While on final approach for landing, the airplane descended below the elevation of the runway threshold. The pilot attempted to conduct a go-around but was unable to prevent a collision with the rising terrain. Detailed examination of the airframe and engine did not reveal evidence of any pre-impact mechanical deficiencies or failures that would have precluded normal operation. The airport's website contained information for pilots about its unique operational hazards. The website explicitly warned that there were no visual cues for altitude reference on approach, that there was usually a strong downdraft near the approach end of the runway due to the surrounding terrain and prevailing winds, and that the upslope of the runway could cause approach and flare difficulties for inexperienced pilots. The website further stated that most flying clubs required pilots flying into the airport for the first time to be accompanied by a flight instructor or another pilot familiar with the airport. The pilot reported that the accident flight was his first experience flying to that airport, and that neither his co-owners of the airplane, nor his insurance company, required any checkout flight to that airport. He reported that he was only vaguely aware of the visual illusions associated with the landing approach; and that he was unaware of, and never saw or used, the pulsating visual approach slope indicator (PVASI) with which the runway was equipped. Review of onboard GPS data revealed that the pilot flew a straight-in approach, instead of the normal and recommended right traffic pattern. The airplane joined the final approach course about 1.4 miles from the runway threshold and about 100 ft below the nominal approach path slope. The airplane descended farther below the nominal approach path and remained in the PVASI flashing red (well below course) indication zone for the entire approach. The pilot initiated the go-around about 8 seconds before impact, as the airplane descended below the elevation of the threshold. The pilot's incomplete preparations for the flight, particularly with regard to the airport's peculiarities and associated hazards, resulted in the pilot conducting an inordinately low final approach. Had the pilot flown the recommended traffic pattern instead of a straight-in approach, he would have provided himself with another opportunity to detect the airport's unusual characteristics and conduct his final approach accordingly. Finally, ground and wind speed data suggest that the airplane was near or at the extreme low end of its normal approach speed range just before the go-around. In combination, these factors placed the airplane in a position and energy state from which recovery was difficult or impossible once the airplane encountered the known downdraft phenomenon just short of the runway threshold.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 31 Mar 2016 | Cessna 172 | Madrid, Spain | - | Fatal | 3 |
| 20 Aug 2016 | Cessna 172 | Anchorage, Alaska, United States | - | No injuries | - |
| 12 Jan 2016 | Cessna 172 | Dothan, Alabama, United States | Embry Riddle Aeronautical University Inc | No injuries | - |
| 1 Jul 2016 | Cessna 172RG | Manhattan, Kansas, United States | - | No injuries | - |
| 8 Oct 2016 | Cessna 172 | Ocean Springs, Mississippi, United States | - | No injuries | - |
| 19 May 2016 | Cessna 172 | Newport News, Virginia, United States | Freedom Aviation | No injuries | - |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 6 Oct 2016 | Joe Salomone SUPER CUB SQ2 | Boca Reservoir, California, United States | - | No injuries | - |
| 12 Dec 2016 | Cessna T210M | Mecca, California, United States | - | Serious injuries | - |
| 25 Aug 2016 | Siai-Marchetti SF260 | Fullerton, California, United States | Air Combat, USA | Minor injuries | - |
| 15 Dec 2016 | Bombardier CL 600 2B19 | San Francisco, California, United States | Skywest Airlines Inc | Unknown | - |
| 24 Aug 2016 | Cessna 182 | Fallbrook, California, United States | Civil Air Patrol Inc. | Minor injuries | - |
| 8 Jul 2016 | Cessna 172 | San Diego, California, United States | - | No injuries | - |