Cessna 172P accident near Chester, California, April 28, 2000
On April 28, 2000 at about 10:15 pm local time, a Cessna 172P, registered N216PB, was destroyed in an accident near Chester, California (Rogers Field). It was a personal flight under general aviation rules (Part 91). 4 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's encounter with a wind shear at low altitude, which resulted in a loss of control and a stall/spin. Factors in the accident were the high density altitude and the pilot's lack of experience and training in high density altitude operations. The pilot's decision to takeoff downwind, while reasonable given the nature of the obstacles and terrain on the other runways, set up a situation where decreased safety margins existed and is considered a factor.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 28, 2000 · about 10:15 pm local time · cases in 2000
- Place
- Chester, California · Rogers Field · cases near this airport · map
- Type
- Accident
- Injuries
- 4 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172P · all 172Ps on the register
- Registration
- N216PB · registry record · serial 17274440
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
There were no witnesses to the accident. A passing motorist saw the tail of the aircraft sticking out of a lake and notified authorities. Crush lines on the recovered wreckage disclosed that it impacted the water right wing low with a pitch attitude in excess of 45 degrees nose down. No preimpact mechanical malfunctions or failures were identified. The pilot rented the airplane and flew 47 miles to the mountain resort airport, landed, met some of his future in-laws, and loaded three of them onboard for a local sightseeing trip around the lake. He obtained his fixed wing private certificate 2 weeks prior to the accident, and this was the first flight with passengers. During training, he had only 1 flight involving a high-density altitude airport, with the balance of his training conducted at airports with elevations less than 1,000 feet msl. The density altitude at the accident site was 5,400 feet. The lake is in an oval shaped mountain valley 25 miles long by 15 miles wide surrounded by mountains, which rise 3,000 to 4,000 above the water's surface. The town and the airport are at the northwest end of the lake. The town borders the airport to the north, and mature pine trees that are 50 to 60 feet in height surround the field and provide obstacles for an approach or departure on any runway but 16/34. The airport manager said that because of the terrain and obstacles, and the proximity of the noise sensitive town to the north, pilots typically land on runway 34 and takeoff on runway 16. While he could not be certain, the airport manager believes the airplane departed on runway 16. The location of the wreckage would be consistent with an upwind to crosswind turn point for runway 16. The aircraft was found in a takeoff and initial climb configuration. Based on the aircraft's recording hour meter and the stopped electric clock, the accident occurred in the initial climb from takeoff on runway 16. The performance data for the airplane establishes it would have climbed to between 400 and 500 feet agl as it reached the accident location. Using flight planning charts for the airplane, the elapsed time on the recording hour meter does not support a conclusion that the pilot completed a run-up or had any appreciable ground run time prior to the accident takeoff. Between 1500 and 1600, the airport's automatic weather observation station recorded winds from 289 degrees at 9 mph with peak gusts to 23 mph. The system only records the highest peak wind gust during the hour-long observation period; however, it does not record the time of the wind peak. Surface winds are affected by friction and Coriolis deflection, which will produce an average increase in wind speed of 10 mph at the boundary between the layer next to the surface and the free flow layer above, which is typically about 400 feet agl. Coriolis deflection will cause the wind direction to change clockwise at the boundary, with a typical direction change of 10 to 20 degrees. Katabatic wind effects in mountainous areas can result in a rapidly moving air mass, which if an inversion layer is present, may flow over the lower layer. Therefore, the takeoff roll on runway 16 would have been with a right quartering tailwind, which moved closer to a direct tailwind and increased in speed as the aircraft climbed through 400 feet. Considering the recorded peak wind speed, it is likely the aircraft encountered a rapid change in wind velocity by as much as 25 to 30 mph. The flaps-up stall speed at zero degrees of bank is 44 knots indicated airspeed (KIAS) and 47 KIAS with 30 degrees of bank angle. Normal initial climb segment airspeed is 74 KIAS at 5,000 feet msl.
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
Pilot
- Certificate: private
- Ratings: single-engine land; rotorcraft: helicopter
- Flight time: 131 hours in all; 63 in this make and model; 15 in the last 90 days; 7 in the last 30 days; 53 as pilot in command
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 9,005 hours
- Last inspection: annual inspection, February 4, 2000; 171 hours since
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320-D2J (piston); 0 hours total
- Operator: Pacific Flight Services
The flight
- Departed from: O05 at 10:30 pm
- Flight plan: none
- Runway 34, 5,000 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 300° at 10 knots
- Visibility: 10 statute miles
- Sky: not recorded; scat at 4,000 ft
- Temperature: 147°F (64°C), dew point 86°F (30°C)
- Altimeter: 30.00 inHg
- Observation at 11:50 pm from CIC, 46 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N216PB the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N216PB on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,687 registered today · the model family and its accident history
- Cessna 72,682 aircraft on the register
- Engine: Lycoming O-320-D2J 96 aircraft carry this series today · as the NTSB recorded it
- Rogers Field · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,097 in the last ten years
- California 27,897 aircraft registered
- Other NTSB records under N216PB 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/LAX00FA178.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
