The U.S. aircraft register, updated daily
Accidents · NTSB CEN26LA333 · Preliminary: the investigation is not finished

Fairchild 24H accident near Indianapolis, Indiana, September 26, 2026

On September 26, 2026 at about 2:30 pm local time, a 1937 Fairchild 24H, registered N16902, was substantially damaged in an accident during landing (landing roll) near Indianapolis, Indiana (Eagle Creek Airpark 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 NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
September 26, 2026 · about 2:30 pm local time · cases in 2026
Place
Indianapolis, Indiana · Eagle Creek Airpark · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Fairchild 24H, built 1937 · all 24Hs on the register
Registration
N16902 · registry record · serial 3211
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On September 26, 2026, about 1430 central daylight time, a Fairchild 24H, N16902, was substantially damaged when it was involved in an accident near Indianapolis, Indiana. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. During the landing rollout shortly after the tailwheel settled to the ground, the pilot reported that the airplane drifted to the right. The pilot pushed the left rudder pedal and the left pedal felt stuck. The airplane departed the right side of the runway into the grass. It continued to the right hit a ditch and hill which resulted in the main landing gear collapse and substantial damage to the fuselage. Postaccident examination of the airplane revealed that a bent piece of metal, possibly a bellcrank travel stop, on the airplane’s structure was making contact with the rudder bellcrank near the rudder pedals. Wear marks were present in the bellcrank that indicated the issue had been occurring for some time. The movement and contact between the two parts made a clicking noise and repeated movement of the rudder pedals resulted in the rudder bellcrank sticking during movement. Sometimes it would become lodged and require force to release the pedal. The airplane was retained for further examination.

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. Flight control sys malf/fail during landing (landing roll) defining event

The aircraft

  • Seats: 3
  • Landing gear: fixed

The flight

  • Runway 03, 4,200 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 70°F (21°C), dew point 43°F (6°C)
  • Altimeter: 30.11 inHg
  • Observation at 7:00 pm from KEYE

Weather report (METAR): METAR KEYE 262253Z AUTO 01003KT 10SM CLR 21/06 A3011 RMK AO2 SLP193 T02110056

Injuries

FatalSeriousMinorNone
Flight crew2

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

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/CEN26LA333.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.