The U.S. aircraft register, updated daily
Accidents · NTSB WPR16LA093 · Final report

Cessna 172 accident near Avalon, California, April 17, 2016

On April 17, 2016 at about 11:29 pm local time, a 1969 Cessna 172, registered N7133G, was destroyed in an accident during approach near Avalon, California (Airport In The Sky). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 17, 2016 · about 11:29 pm local time
Place
Avalon, California · Airport In The Sky · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 K, built 1969 · all 172s on the register
Registration
N7133G · no longer on the register · serial 17258833
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision with terrain or object (not controlled flight into terrain) during approach (VFR pattern final)
  2. Collision with terrain or object (not controlled flight into terrain) during approach (VFR go-around)
  3. Collision with terrain or object (not controlled flight into terrain) during approach
  4. Miscellaneous/other during approach defining event
  5. Miscellaneous/other during landing

The NTSB's findings

  • cause Personnel issues › Task performance › Planning/preparation › (general) › Pilot
  • cause Personnel issues › Experience/knowledge › Knowledge › Knowledge of geographic area › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 174 hours in all; 84 in this make and model; 5 in the last 90 days; 1 in the last 30 days; 117 as pilot in command
  • Medical certificate: Class 3
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 4,952 hours
  • Last inspection: annual inspection, January 3, 2016
  • Maximum gross weight: 2,300 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 E2D (piston); 4,952 hours total

The flight

  • Departed from: LGB Long Beach CA at 11:00 pm
  • Destination: KAVX Avalon CA
  • Flight plan: none
  • Runway 22, 3,000 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 250° at 14 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 3002°F (1650°C)
  • Observation at 11:51 pm from AVX

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

31 documents, released by the NTSB on October 4, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
2 Record of Conversation - Pilot PDF, 2 pages View Download
3 Metars PDF, 1 page View Download
4 Record of Conversation - Eyewitness PDF, 2 pages View Download
5 Record of Conversations - Rescue Coordination Centers PDF, 1 page View Download
6 Record of Conversation - Caltrans PDF, 1 page View Download
7 ELT Position Solutions PDF, 2 pages View Download
8 Email re ELT PDF, 2 pages View Download
9 Record of Conversation Leo and Pilot PDF, 1 page View Download
10 Published Airport Information PDF, 3 pages View Download
11 Avx Runway 22 Slope Information PDF, 2 pages View Download
12 Pvasi Beam Height Diagram PDF, 1 page View Download
13 Email re Pvasi PDF, 3 pages View Download
14 Avx Runway 22 Accidents PDF, 1 page View Download
15 Co Owner Email re CG and Fuel PDF, 2 pages View Download
16 Weight and Balance PDF, 2 pages View Download
17 Owner Provided Performance Data Sheet PDF, 1 page View Download
18 Pilot Email re Approach Speeds PDF, 1 page View Download
19 Pilot Responses to NTSB Questions PDF, 1 page View Download
20 Tracklog Data File data file Download
21 Accident Flight Kml File map file Download
22 Final Approach Track File spreadsheet Download
23 Pvasi Calculations File spreadsheet Download
24 GPS and Approach Information PDF, 11 pages View Download
25 Pilot Email re Traffic Pattern PDF, 1 page View Download
26 Airframe and Engine Examination PDF, 37 pages View Download
27 Cabin Contents and Documentation PDF, 13 pages View Download
28 Maintenance Records Excerpts PDF, 14 pages View Download
29 Statement of Party Representatives to NTSB Investigation PDF, 2 pages View Download
30 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
31 Accident and Site Images PDF, 11 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.