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

Cessna 172S accident near Oceanside, California, January 24, 2009

On January 24, 2009 at about 6:42 pm local time, a Cessna 172S, registered N562AD, was substantially damaged in an accident during enroute (cruise) near Oceanside, California (Oceanside Municipal Airport). 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

A defective alternator wire splice that resulted in an intermittent electrical system malfunction and erroneous fuel gauge readings, and, a loss of engine power for an undetermined reason.

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

What the record shows

Date
January 24, 2009 · about 6:42 pm local time · cases in 2009
Place
Oceanside, California · Oceanside Municipal Airport · cases near this airport · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Cessna 172S · all 172Ss on the register
Registration
N562AD · no longer on the register · serial 172S9549
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was on an instrument clearance in cruise flight at 6,000 feet mean sea level above a cloud layer. He said that while he did not see any fuel leaking, the fuel gauges were moving steadily toward zero at a higher rate than normal. He moved the fuel selector to the right tank position, yet the fuel gauges still kept moving rapidly toward zero. The pilot then attempted to make a radio call to declare an emergency; however, there was a complete electrical failure. He decided to make an emergency landing at a nearby airport, and as he started descending, the engine lost power. The pilot said that since the airplane was above clouds, he could not see the airport until the airplane was directly above it. As he approached runway 24, he realized he was too high and fast, so he overflew the runway and reversed course at the west end of the airport to attempt a landing on runway 06. He was too high and fast to land on runway 06 and did not have enough altitude or airspeed to make another attempt on runway 24. The airplane impacted the ground and obstacles about 0.5 miles east of the airport. During post-accident examination, fuel was found in both wing tanks and in the firewall-mounted fuel strainer. No evidence of significant fuel leakage was noted. No evidence was found of any mechanical malfunctions or failures that would have prevented the engine from producing power. The reason for the reported loss of engine power could not be determined. A defective splice repair to the alternator output electrical wire was observed, and when the wire was removed, the splice came apart and revealed evidence of electrical arcing. The alternator was bench tested and found to be functional. The defective splice likely resulted in the anomalous fuel gauge readings noted by the pilot. The fact that air traffic control reported the airplane’s transponder was broadcasting the codes for radio failure and then for emergency as the airplane descended indicates the airplane had not lost all electrical power. The pilot’s inability to communicate by radio during the descent likely resulted from his improper positioning of avionics bus 1 switch to the OFF position where it was found, which would have cut off power to communications radio 1.

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. Sys/Comp malf/fail (non-power) during enroute (cruise) defining event
  2. Loss of engine power (total) during emergency descent
  3. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Aircraft › Aircraft systems › Electrical power system › Electrical pwr sys wiring › Damaged/degraded other cases naming the electrical power
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • cause Aircraft › Aircraft systems › Fuel system › Fuel quantity indicator › Malfunction other cases naming the fuel system

Pilot

  • Certificate: commercial pilot, private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 299 hours in all; 155 in this make and model; 16 in the last 90 days
  • Last flight review: April 20, 2008
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

Crew member

  • Certificate: student
  • Flight time: 70 hours in all
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 4,760 hours
  • Last inspection: 100-hour inspection, January 23, 2009; 2 hours since
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-360-L2A (piston); 0 hours total

The flight

  • Departed from: SEE El Cajon CA at 6:21 pm
  • Destination: OKB Oceanside CA
  • Flight plan: IFR
  • Runway 06, 2,712 ft by 75 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 260° at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 1,800 ft; a few clouds at 1,100 ft
  • Temperature: 63°F (17°C), dew point 54°F (12°C)
  • Altimeter: 30.20 inHg
  • Observation at 6:55 pm from OKB, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

9 documents, released by the NTSB on August 31, 2009. 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.

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

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR09LA098.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.