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

Piper PA 24-260 accident near Fargo, North Dakota, February 8, 2018

On February 8, 2018, a 1969 Piper PA 24-260, registered N9360P, was substantially damaged in an accident during enroute near Fargo, North Dakota (Hector Intl airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to use the published emergency procedures to manually extend the landing gear when an electrical failure precluded normal extension of the landing gear, resulting in the gear collapse during landing. Contributing to the accident was the pilot’s failure to ensure, before takeoff, that the battery was fully charged after its depletion due to a faulty alternator.

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

What the record shows

Date
February 8, 2018
Place
Fargo, North Dakota · Hector Intl · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA 24-260, built 1969 · all PA 24-260s on the register
Registration
N9360P · no longer on the register · serial 24-4860
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot taxied the airplane to the airport jet center to pick up a passenger for a personal flight. When leaving the jet center, the airplane's engine did not start. A ground power unit was used to charge the airplane's battery to start the engine. The pilot verified that the battery was charging. The pilot then taxied the airplane to the runway and performed an engine run-up but did not verify before takeoff that the battery was fully charged by checking the ammeter indication. After departure and after raising the landing gear, the pilot realized that he did not receive a radio call from the tower controller and noticed that all of the radios were inoperative, which indicated a loss of electrical power. The pilot subsequently re-entered the traffic pattern and rocked the airplane's wings to provide an indication to the tower controller of the radio difficulties. The controller provided a green light to indicate that the airplane was cleared to land, and the pilot used normal procedures for the landing. However, due to the loss of electrical power, the pilot initiated an emergency gear extension but was unable to remove the cover plate over the emergency gear handle. The pilot then bent the cover back, placed the emergency extension rod into the right hole on the torque tube, and rocked the rod back and forth. The pilot checked the mirror on the airplane's wing tip, and the landing gear appeared to be down. When the airplane touched down on the runway, the landing gear collapsed, and the airplane slid off the runway and impacted a runway sign, causing substantial damage to the airplane. The pilot did not use the emergency procedures in the airplane flight manual or abbreviated checklist to properly extend the gear despite being trained to do so. An examination of the electrical system revealed that a faulty alternator caused the electrical failure and that the battery was not fully charged before takeoff.

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. Electrical system malf/failure during enroute defining event
  2. Landing gear collapse during landing
  3. Runway excursion during landing (landing roll)
  4. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
  • cause Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Incorrect use/operation
  • factor Aircraft › Aircraft systems › Electrical power system › Battery/charger › Failure
  • factor Aircraft › Aircraft systems › Electrical power system › AC generator › alternator › Failure
  • factor Personnel issues › Task performance › Inspection › Preflight inspection › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 111 hours in all; 5.6 in this make and model; 12.3 in the last 90 days; 29.5 as pilot in command
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection
  • Maximum gross weight: 3,200 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming TIO-540-D4A5 (piston); 8,340 hours total

The flight

  • Departed from: FAR Fargo ND at 11:40 pm
  • Destination: FAR Fargo ND
  • Flight plan: none
  • Runway 18, 9,001 ft by 150 ft

Weather at the time

  • Light: dusk
  • Wind: from 190° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 3°F (-16°C), dew point -4°F (-20°C)
  • Altimeter: 30.29 inHg
  • Observation at 11:57 pm from KFAR

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

5 documents, released by the NTSB on April 19, 2018. 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.

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.