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

Aviat Husky accident near Greenfield, Indiana, June 23, 2009

On June 23, 2009 at about 7:00 pm local time, a Aviat Husky, registered N263AL, was substantially damaged in an accident during takeoff near Greenfield, Indiana (Mt. Comfort Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot failed to maintain directional control of the airplane during the takeoff roll.

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

What the record shows

Date
June 23, 2009 · about 7:00 pm local time · cases in 2009
Place
Greenfield, Indiana · Mt. Comfort Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Aviat Husky
Registration
N263AL · registry record · serial 2427
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that he was departing in a tailwheel-equipped airplane from Runway 25, and the winds were from 050 degrees at 3 knots. He reported that a wind gust lifted the right wing and the airplane veered off the runway. The left wing struck the ground and the airplane spun around. The wing sustained substantial damage.

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 control on ground during takeoff defining event
  2. Runway excursion during takeoff
  3. Collision with terrain or object (not controlled flight into terrain) during takeoff

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Response/compensation

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,138 hours in all; 41 in this make and model; 5 in the last 90 days; 3 in the last 30 days
  • Medical certificate: Class 3

The aircraft

  • Landing gear: fixed
  • Engine: Lycoming IO-360-A1D6 (piston); 0 hours total

The flight

  • Departed from: MQJ Greenfield IN at 7:00 pm
  • Destination: MQJ Greenfield IN
  • Flight plan: none
  • Runway 25

Weather at the time

  • Light: daylight
  • Wind: from 050° at 3 knots
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

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

1 document, released by the NTSB on July 24, 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/CEN09CA420.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.