Luscombe 8 accident near Huntingburg, Indiana, October 12, 2016
On October 12, 2016 at about 1:42 pm local time, a 1941 Luscombe 8, registered N39083, was substantially damaged in an accident during landing (landing roll) near Huntingburg, Indiana (Huntingburg 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 pilot’s delayed crosswind correction during the landing roll with a gusting left crosswind, which resulted in the airplane weathervaning and nosing over.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 12, 2016 · about 1:42 pm local time
- Place
- Huntingburg, Indiana · Huntingburg · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Luscombe 8 B, built 1941 · all 8s on the register
- Registration
- N39083 · no longer on the register · serial 1844
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot in the tailwheel-equipped airplane, after a 1-hour-long local flight, he returned to the departure airport and noticed that he would be landing with a gusting, direct left crosswind. He reported that he made one low pass about 20 ft above the ground and that he "felt the airplane was steady." He accomplished a go-around and initiated an approach. He recalled that he made a three-point landing and touched down about 50 mph on the runway centerline. When the wheels touched down, a wind gust lifted the left wing, and he tried to compensate with aileron and throttle, but he "was too slow to regain control of the airplane." He reported that the left wing struck the ground and that the airplane exited the left side of the runway and nosed over. The airplane sustained substantial damage to both wings and the firewall. The METAR at the airport reported that, at the time of the accident, the wind was from 180° at 11 knots, gusting to 16 knots. The airplane landed on runway 27. According to the FAA-H-8083-3B Airplane Flying Handbook, "Crosswind After-Landing Roll," pages 8-15 and 8-16: Retaining control on the ground is a critical part of the after-landing roll, because of the weathervaning effect of the wind on the airplane. While the airplane is decelerating during the after-landing roll, more and more aileron is applied to keep the upwind wing from rising. Since the airplane is slowing down, there is less airflow around the ailerons and they become less effective. At the same time, the relative wind is becoming more of a crosswind and exerting a greater lifting force on the upwind wing. When the airplane is coming to a stop, the aileron control must be held fully toward the wind. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
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
- Loss of control on ground during landing (landing roll) defining event
- Abnormal runway contact during landing (landing roll)
- Runway excursion during landing (landing roll)
- Nose over/nose down during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Crosswind correction › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 210 hours in all; 18 in this make and model; 210 as pilot in command
- Last flight review: September 8, 2015
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 1,838 hours
- Last inspection: annual inspection, November 4, 2015
- Maximum gross weight: 1,400 lb
- Seats: 2
- Landing gear: fixed
- Engine: Continental C-90 12-F (piston); 837 hours total
The flight
- Departed from: HNB Huntingburg IN at 12:35 pm
- Destination: HNB Huntingburg IN
- Flight plan: none
- Runway 27, 5,000 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 180° at 12 knots, gusting 16
- Visibility: 10 statute miles
- Temperature: 63°F (17°C), dew point 46°F (8°C)
- Altimeter: 30.19 inHg
- Observation at 1:55 pm from KHNB
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on June 14, 2017. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Photo (Courtesy of FAA) | PDF, 1 page | View Download |
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.