# NTSB GAA17CA021: Luscombe 8, N39083, Huntingburg, IN, October 12, 2016 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: October 12, 2016, 09:42 local (13:42 UTC) - Place: Huntingburg, IN - Coordinates: 38.249168, -86.953613 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.2492&lon=-86.9536&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report July 5, 2017 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 94199 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA17CA021 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/94199/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=94199 - Page: https://openairdocs.org/ntsb/GAA17CA021 ## Probable cause The pilot’s delayed crosswind correction during the landing roll with a gusting left crosswind, which resulted in the airplane weathervaning and nosing over. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: crosswind correction](https://openairdocs.org/ntsb-findings/01062030): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-findings/01062030/cases.md?model=8190106), [All aircraft, 184 cases](https://openairdocs.org/ntsb-findings/01062030/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=8190106), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Luscombe 8B, 2 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=8190106), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=8190106), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=8190106), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=8190106), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-events/090/sequence.md?model=8190106), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Luscombe 8B, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=8190106), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Luscombe 8B, 2 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=8190106), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis 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. ## Factual narrative According to the pilot in the tailwheel-equipped airplane, after an hour long local flight, he returned to the airport from which he had departed, and noticed that he would be landing with a gusting, direct left crosswind. He made one low pass about 20 ft. above the ground, and "I 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 miles per hour on the runway centerline. When the wheels touched down a gust of wind lifted the left wing, and he tried to compensate with aileron and throttle, but reported that he "was too slow to regain control of the airplane". He reported that the left wing struck the ground, the airplane exited the left side of the runway and nosed over. The airplane sustained substantial damage to both wings and the fire wall. The meteorological aerodrome report at the airport, at the time of the accident, was wind 180°, at 11 kts., gusting to 16 kts. The airplane landed on runway 27. According to the FAA-H-8083-3B Airplane Flying Handbook, specifically the section entitled Crosswind After-Landing Roll, pg. 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 pre-accident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N39083](https://openairdocs.org/deregistered/N39083-2020-01-06), registration cancelled 2020-01-06, S/N 1844, built 1941 (OpenAirDocs) - Reported make and model: LUSCOMBE 8 (B) - Registry model: [Luscombe 8B](https://openairdocs.org/model/luscombe-8b) (registry code 8190106) (OpenAirDocs) - Registry engine: [Continental A&C65 series](https://openairdocs.org/engine/continental-a-c65-series) (registry code 17003, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 1844 - Year built: 1941 - Airframe hours: 1838 - Engines: Continental C-90 12-F 90 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 4, 2015 - Departed: HNB, Huntingburg, IN - Destination: HNB, Huntingburg, IN - Airport: HNB, Huntingburg, runway 27, 5,000 × 75 ft, asphalt - Equipment: Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 62; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review September 8, 2015; seat: left; restraint: lap only; flight hours: 210 total, 18 in this make and model, 210 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 180° at 12 knots, gusting 16 - Visibility: 10 statute miles - Temperature: 63 °F, dew point 46 °F - Altimeter: 30.19 inHg - Observed at: KHNB ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20161012020049A](https://openairdocs.org/incident/20161012020049A), Oct 12, 2016: Luscombe 8B, Huntingburg, IN, Substantial damage. On October 12, 2016, at approximately 1000 eastern daylight time (EDT) (1400Z), a Luscombe 8B, sustained substantial damage after impacting the terrain while… ## Docket (2 files) The files NTSB released with the investigation on June 14, 2017, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=94199. 4.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40453104&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photo (Courtesy of FAA) (item 2, .PDF, 1 photo, 141 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40453105&FileExtension=.PDF&FileName=Photo%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.