# NTSB ERA25LA115: Luscombe 8A, N77989, Hampton, NH, February 11, 2025

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Class 3 · Limited · Final report
- Date: February 11, 2025, 10:10 local (15:10 UTC)
- Place: Hampton, NH
- Coordinates: 42.956899, -70.830757
- Nearby events: https://openairdocs.org/map.md?lat=42.9569&lon=-70.8308&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report December 17, 2025
- Report: Approved by Office Director
- Investigation class: Class 3
- NTSB office: Eastern Region Aviation
- Parties: FAA/FSDO
- SAIBs cited in the narratives: [SAIB CE-09-35](https://openairdocs.org/saib/CE-09-35) (OpenAirDocs)
- NTSB case key (mKey): 199683
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA25LA115
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199683/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=199683
- Page: https://openairdocs.org/ntsb/ERA25LA115

## Probable cause

The pilot’s failure to maintain adequate airspeed while maneuvering to land, which resulted in an exceedance of the airplane’s critical angle of attack and subsequent aerodynamic stall.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Luscombe 8A, 39 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=8190104), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Luscombe 8A, 4 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=8190104), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Luscombe 8A, 8 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=8190104), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)

## Analysis

After departing and completing maneuvers in the local area, the pilot was returning to the departure airport to land. According to the pilot and surveillance video of the accident flight, after the pilot aborted his initial landing attempt the airplane climbed at a low speed and high angle of attack before rejoining the traffic pattern at a low altitude. The pilot described that the airplane was climbing at a lower rate than he had expected, and when the airplane turned from the downwind leg toward final approach, it turned and descended continuously into a prevailing right quartering tailwind. The pilot stated that, as the airplane neared the final approach to the runway, the left wing dropped and it felt like the ailerons were not responding. The airplane then descended in a steep left wing and nose low attitude until it impacted the ground short of the runway. Postaccident examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures of the airframe or engine that would have precluded normal operation. Audio recorded during the airplane’s final descent just before impact indicated that the engine was running at a constant rate with no appreciable change in sound. Additionally, a fractured aileron control cable attach bracket displayed evidence of ductile overstress separation, most likely as a result of the airplane’s impact with trees and terrain. While the pilot described that the airplane did not climb as he had expected during the go-around attempt, the lack of any mechanical anomalies found during the postaccident examination of the engine, the audio depicting the engine running continuously just before impact, and the lack of weather conditions conducive to the formation of carburetor icing, all implied no reason for the engine to operate with any degraded capability. However, the transition from the pilot’s initial tailwind landing attempt to a go-around as depicted by the surveillance video showed the airplane in relatively extreme bank and pitch attitudes that suggested the airplane was being operated at a low airspeed and close to an aerodynamic stall. Further, the airplane’s loss of altitude as it turned on the final leg of the approach to the runway, the subsequent drop of the left wing described by the pilot, and the pilot’s sensation that the ailerons were not responding were all consistent with a loss of airspeed and subsequent aerodynamic stall.

## Factual narrative

On February 11, 2025, about 1010 eastern standard time, a Luscombe 8A, N77989, was substantially damaged when it was involved in an accident at Hampton Airfield (7B3), Hampton, New Hampshire. The private pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot had planned a brief local flight, and despite noting a slight tailwind was prevailing for runway 2 at 7B3, elected to depart on that runway as other traffic at the airport was already utilizing it. After performing some maneuvers, he returned to the departure airport with the carburetor heat activated and approached runway 2 for landing. During the landing approach, the pilot felt as though the airplane’s “…sink rate was high and felt like I possibly had a downwind condition or carburetor icing condition.” He aborted the landing attempt, and with the carburetor heat still engaged, the pilot described that the airplane’s climb rate was poor (200 fpm vs. its usual 1,100 fpm). The pilot then proceeded around the airport traffic pattern for a “short approach” to runway 2. While on short final approach to land, the airplane’s left wing dropped and it felt to the pilot as if the ailerons were not responding. The pilot attempted to regain control of the airplane but it subsequently impacted a tree. An airport surveillance video depicted the pilot’s initial low approach to runway 02, after which it exited from the camera’s view behind a row of hangars. When the airplane came back into view, the airplane was just above the runway, in a steep right bank, nose up attitude, with the right wingtip near the runway and the left main landing gear and left wing in the air. The airplane then began to climb at a relatively low speed and relatively high pitch angle. When the airplane came back into the frame, it was on a low-altitude downwind leg with the windsock showing a right quartering headwind (or a right quartering tailwind relative to runway 02). The airplane then began a continuous descending left turnback toward the runway before descending below a tree line and out of the camera’s view. A second video from a residential security camera located about 575 ft from the approach end of runway 2 showed the airplane immediately before it impacted the ground. The airplane was in a steep left wing and nose down attitude, and was in a steep angle of descent. The airplane subsequently impacted a stand of trees and the ground. During the video, the engine could be heard running at a constant rate with no appreciable change in sound until it impacted the trees. The airplane’s fuselage, wings, and tail were substantially damaged during the accident. A Federal Aviation Administration inspector examined the airplane at the accident site and confirmed continuity of the flight controls. The inspector observed little movement of the left aileron as it was obstructed by tree branches. Further examination of the wreckage after it had been recoveredfrom the accident site revealed a mixture of automotive fuel and 100 LL aviation fuel in the fuel system. The mixture showed no evidence of water or debris. All the engine’s cylinders had compression when tested with a compression test gauge. Spark was observed on the top spark plugs by rotating the engine’s crankshaft through the firing order. The right magneto was removed, and the impulse coupling was manually rotated, which produced spark to the remaining four spark plugs. The spark plugs exhibited normal wear with no evidence of fouling when compared to the Champion Aviation Check-A-Plug chart. No evidence of any preaccident mechanical malfunctions or failures were found that would have precluded normal engine operation. Examination of the airframe found that the right wingtip had sustained flattening impact damage at the outboard rear corner. The left wing had leading edge damage consistent with impact. The left lower aileron control cable bracket was found to be fractured into two pieces. Examination of the aileron control cable attach bracket found evidence of fracture consistent with ductile overstress. The bracket was bent adjacent to the fracture consistent with out-of-plane bending loads. The empennage sustained impact damage from the stabilizers forward. No evidence of any preaccident mechanical malfunctions or failures were found with the airframe that would have precluded normal operation. At 1055, the weather reported at 7B3, about 3 miles east of the accident site, included a temperature of -3°C and a dew point -12°C. The calculated relative humidity at this temperature and dewpoint was 50 percent. Review of the icing probability chart contained within Federal Aviation Administration Special Airworthiness Information Bulletin CE-09-35 revealed the atmospheric conditions at the time of the accident were not conducive to carburetor icing.

## Aircraft

- Registration: [N77989](https://openairdocs.org/aircraft/N77989), registered now, S/N 3716, built 1946 (OpenAirDocs)
- Reported make and model: LUSCOMBE 8A
- Registry model: [Luscombe 8A](https://openairdocs.org/model/luscombe-8a) (registry code 8190104) (OpenAirDocs)
- Registry engine: [Continental A&C65 series](https://openairdocs.org/engine/continental-a-c65-series) (registry code 17003, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 3716
- Year built: 1946
- Airframe hours: 1583.03
- Engines: CONTINENTAL MOTOR C-85-12F 65 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, August 1, 2024, 7.5 hours before
- Destination: Same as departure
- Airport: 7B3, Hampton Airfield, runway 02, 2,105 × 121 ft, asphalt
- Equipment: Handheld GPS

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 66; injuries: none; private; airplane ratings: single-engine land; medical: sport pilot; last flight review September 2, 2024; seat: left; restraint: 3-point; flight hours: 545 total, 345 in this make and model, 545 as pilot in command, 6.5 in the last 90 days, 1.4 in the last 30 days, 0.5 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 250° at 9 knots
- Visibility: 10 statute miles
- Lowest ceiling: 25,000 ft broken
- Temperature: 27 °F, dew point 10 °F
- Altimeter: 30.33 inHg
- Turbulence: Moderate
- Observed at: PSM, 8 nm away
- METAR: KPSM 111555Z 25009KT 10SM BKN250 M03/M12 A3033 RMK AO2A SLP275 T10291116

## 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 20250211000739A](https://openairdocs.org/incident/20250211000739A), Feb 11, 2025: Luscombe 8A, Hampton, NH, Substantial damage. A light sport airplane departed 7B3 (north Hampton, NH) on runway 02 at approximately 0950 on 02/11/2025. The airplane did a short scenic flight and entered…

## Other investigations on N77989 (1)

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.

- [NTSB UNK64X3265](https://openairdocs.org/ntsb/UNK64X3265), Aug 8, 1964: Luscombe 8A (N77989), Westboro, MA, substantial damage

## Docket (8 files)

The files NTSB released with the investigation on December 17, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=199683. 30.3 MB in all.

- Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19178546&FileExtension=pdf&FileName=6120_1_Form-2-1_Redacted-Rel.pdf
- Airport surveillance video (item 2, MOV, 7.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18941818&FileExtension=mov&FileName=Video-Rel.mov
- Residential security camera video (item 3, MOV, 15.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18941714&FileExtension=mov&FileName=1739293334video_share%20(1)-Rel.mov
- Investigation photographs (item 4, PDF, 4 pages, 942 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18361575&FileExtension=pdf&FileName=Investigation%20Photographs-Rel.pdf
- Memorandum for record a�� wreckage and engine exam summary (item 5, PDF, 6 pages, 2.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19643980&FileExtension=pdf&FileName=NTSB%20Engine%20and%20Fuel%20System%20Exam-Rel.pdf
- FAA inspector's statement (item 6, PDF, 1 page, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18940792&FileExtension=pdf&FileName=20250616%20Lindsey%20Morrissey%20Inspector%20Statement-Rel.pdf
- Memorandum for record - materials laboratory examination (item 7, PDF, 2 pages, 165 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19646432&FileExtension=pdf&FileName=MOR%20Mat%20Lab-Rel.pdf
- Wreckage release and evidence control documentation (item 8, PDF, 3 pages, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19178405&FileExtension=pdf&FileName=Wreckage%20release%20final_Redacted-Rel.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.
