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

Piper PA-22-135 accident near Wellington, Kansas, June 1, 2010

On June 1, 2010 at about 3:00 am local time, a Piper PA-22-135, registered N1821P, was destroyed in an accident during standing (engine(s) start-up) near Wellington, Kansas (Wellington Municipal airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A fire of undetermined cause that originated in the airplane's cabin.

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

What the record shows

Date
June 1, 2010 · about 3:00 am local time
Place
Wellington, Kansas · Wellington Municipal · map
Type
Accident
Injuries
1 person had minor injuries; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-135 · all PA-22-135s on the register
Registration
N1821P · no longer on the register · serial 22-2601
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot said that he had made two touch-and-go landings. As he applied power to take off, the airplane "would not accelerate." He stopped the airplane on the runway and the engine quit. He used the primer and attempted to restart the engine. His passenger then noticed a fire under the instrument panel. Both occupants evacuated the airplane. Fire inspectors examined the airplane but were unable to determine either the origin or cause of the fire, but it was noted that the most intense portion of the fire was in the cabin area. The pilot held a student pilot certificate that expired in 2004. He did not hold a valid Federal Aviation Administration medical certificate and refused to complete the NTSB Operator Aircraft Accident/Incident Report form.

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. Fire/smoke (non-impact) during standing (engine(s) start-up) defining event

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Personnel issues › Experience/knowledge › Experience/qualifications › Qualification/certification › Pilot

Pilot

  • Flight time: 170 hours in all; 170 in this make and model
  • Medical certificate: None
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 2,241 hours
  • Last inspection: annual inspection, July 18, 2009; 73 hours since
  • Maximum gross weight: 1,850 lb
  • Seats: 4
  • Landing gear: fixed
  • Fire on the ground

The flight

  • Departed from: K50 Derby KS at 2:15 am
  • Destination: K50 Derby KS
  • Flight plan: none
  • Runway 35, 4,200 ft by 100 ft

Weather at the time

  • Light: night
  • Wind: from 130° at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 22,000 ft; a few clouds at 4,600 ft
  • Temperature: 75°F (24°C), dew point 66°F (19°C)
  • Altimeter: 29.90 inHg
  • Observation at 2:53 am from ICT, 25 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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.

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.