The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA25LA115 · Final report

Luscombe 8A accident near Hampton, New Hampshire, February 11, 2025

On February 11, 2025 at about 3:10 pm local time, a 1946 Luscombe 8A, registered N77989, was substantially damaged in an accident during approach (VFR pattern final) near Hampton, New Hampshire (Hampton Airfield). 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).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

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.

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

What the record shows

Date
February 11, 2025 · about 3:10 pm local time
Place
Hampton, New Hampshire · Hampton Airfield · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Luscombe 8A, built 1946 · all 8As on the register
Registration
N77989 · registry record · serial 3716
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

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.

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 in flight during approach (VFR pattern final) defining event

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 545 hours in all; 345 in this make and model; 6.5 in the last 90 days; 1.4 in the last 30 days; 545 as pilot in command
  • Last flight review: September 2, 2024
  • Medical certificate: Sport Pilot
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 1,583.0 hours
  • Last inspection: annual inspection, August 1, 2024; 7.5 hours since
  • Maximum gross weight: 1,260 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Continental Motor C-85-12F (piston); 0 hours total

The flight

  • Flight plan: none
  • Runway 02, 2,105 ft by 121 ft

Weather at the time

  • Light: daylight
  • Wind: from 250° at 9 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 25,000 ft
  • Temperature: 27°F (-3°C), dew point 10°F (-12°C)
  • Altimeter: 30.33 inHg
  • Observation at 10:55 am from PSM, 8 miles away

Weather report (METAR): KPSM 111555Z 25009KT 10SM BKN250 M03/M12 A3033 RMK AO2A SLP275 T10291116

Injuries

FatalSeriousMinorNone
Flight crew1

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

8 documents, released by the NTSB on December 17, 2025. 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.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA25LA115.