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

Luscombe 8A accident near Fort Wayne, Indiana, September 4, 2021

On September 4, 2021 at about 6:30 pm local time, a 1947 Luscombe 8A, registered N2071K, was substantially damaged in an accident during initial climb near Fort Wayne, Indiana (Smith Fld airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The total loss of engine power after takeoff due to the formation of carburetor ice while on the ground and the pilot’s failure to apply carburetor heat immediately before takeoff.

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

What the record shows

Date
September 4, 2021 · about 6:30 pm local time · cases in 2021
Place
Fort Wayne, Indiana · Smith Fld · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Luscombe 8A, built 1947 · all 8As on the register
Registration
N2071K · registry record · serial 4798
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot and three other airplanes were conducting a cross-country flight. After refueling, the airplanes taxied to the runway run-up area, and the pilot completed his preflight checklist. Shortly after takeoff, about 200 to 300 ft above ground level, the engine began operating rough, which included some surging, and then lost power. The pilot attempted to land on the opposite runway, which resulted in a landing with a 9- to 12-knot tailwind. Due to the tailwind, the airplane touched down near the end of the runway. Realizing the airplane would not stop before the end of the runway, the pilot turned the airplane to the right and exited the runway surface. The airplane entered a soybean field and nosed over. The airplane sustained substantial damage to the fuselage and vertical stabilizer. Postaccident examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Weather conditions reported at the time of the accident were conducive to serious carburetor icing at glide power. The pilot reported that during the takeoff, the carburetor heat was off. Therefore, it is likely that carburetor ice accumulated during taxi and run-up before the takeoff, which resulted in a loss of engine power.

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. Loss of engine power (total) during initial climb defining event
  2. Collision with terrain or object (not controlled flight into terrain) during emergency descent
  3. Fuel related during initial climb

The NTSB's findings

  • Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Inoperative other cases naming the engine
  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to carburetor icing › Effect on operation
  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 637 hours in all; 257 in this make and model; 637 as pilot in command
  • Last flight review: August 4, 2021
  • Medical certificate: BasicMed (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,143 hours
  • Last inspection: annual inspection, September 25, 2020
  • Maximum gross weight: 1,260 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental Motors C-85 (piston); 0 hours total

The flight

  • Destination: FKL Franklin PA
  • Flight plan: none
  • Runway 05/2, 3,126 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 240° at 16 knots, gusting 25
  • Visibility: 10 statute miles
  • Sky: broken clouds at 5,000 ft; a few clouds at 3,000 ft
  • Temperature: 72°F (22°C), dew point 61°F (16°C)
  • Altimeter: 29.94 inHg
  • Observation at 2:54 pm from KFWA, 1 miles away

Weather report (METAR): KFWA 041854Z 24016G25KT 10SM FEW030 BKN050 OVC095 22/16 A2994 RMK AO2 SLP134 T02220161 $

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

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

7 documents, released by the NTSB on January 27, 2023. 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.

Other NTSB records under N2071K the same tail number, which may have belonged to a different aircraft at the time

1985-07-25CHI85LA313 · accident near Valparaiso, IN · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

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