Grumman American Avn. CORP. AA-5A accident near Gladewater, Texas, February 18, 2025
On February 18, 2025 at about 4:15 am local time, a 1977 Grumman American Avn. CORP. AA-5A, registered N26071, was substantially damaged in an accident during initial climb near Gladewater, Texas. 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 NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 18, 2025 · about 4:15 am local time · cases in 2025
- Place
- Gladewater, Texas · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Grumman American Avn. CORP. AA-5A, built 1977 · all AA-5As on the register
- Registration
- N26071 · registry record · serial AA5A0413
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On February 17, 2025, about 2215 central standard time, a Grumman AA-5A airplane, N26071, was substantially damaged when it was involved in an accident near Gladewater, Texas. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, the airplane engine lost partial power about 450 to 500 ft above ground level during the initial takeoff climb. The pilot immediately made a left turn back towards the airport and conducted a slow but controlled descent with the remining engine power. He chose to continue the turn and performed a forced landing to the grass next to the runway which resulted in substantial damage to the left wing and empennage. The pilot stated that he was ferrying the airplane to the Rusk County Airport (RFI) in Henderson, Texas, to have engine maintenance performed. The pilot further stated that the carburetor had been replaced about two weeks prior, and the airplane was experiencing a slight engine stumbling at full power and full mixture on subsequent flights. Postaccident examination of the engine revealed that the carburetor inlet rubber duct between the airbox and carburetor was puckered inward at both the airbox outlet and carburetor inlet. The puckering of the duct was observed to be partially blocking the carburetor venturi. Figure 1. View through the carburetor. The airplane was retained for further examination.
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 engine power (partial) during initial climb defining event
- Off-field or emergency landing during initial climb
The aircraft
- Seats: 4
- Landing gear: fixed
The flight
- Destination: KRFI Henderson TX
- Runway 14, 3,299 ft by 75 ft
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 43°F (6°C), dew point 32°F (0°C)
- Altimeter: 30.11 inHg
- Observation at 10:12 pm from KJXI, 10 miles away
Weather report (METAR): KJXI 180635Z AUTO 00000KT 10SM CLR 06/00 A3011 RMK AO2 T00621001
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Airplane Accident Overview
Photograph 2 – Rubber Duct Puckering
Photograph 3 – Carburetor Side of Duct
Photograph 4 – Airbox Side of DuctThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
8 documents, released by the NTSB on November 12, 2026. 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, 10 pages | View Download |
| 2 | Examination Summary | PDF, 9 pages | View Download |
| 3 | Photo Array | PDF, 5 pages · our copy | View Download |
| 4 | Maintenance Records - Engine Logbook Excerpts | PDF, 8 pages | View Download |
| 5 | Maintenance Records - Airframe Logbook Excerpts | PDF, 12 pages | View Download |
| 6 | Maintenance Mor | PDF, 2 pages | View Download |
| 7 | Grumman SB-175 | PDF, 1 page | View Download |
| 8 | AA-5A Maintenance Manual Excerpts | PDF, 2 pages | View Download |
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
- N26071 on the register today · the tail number may have moved to another aircraft since
- Grumman American Avn. Corp. AA-5 Traveler, Cheetah and Tiger 1,286 registered today · the model family and its accident history
- Gladewater Municipal · nearest airport
- Rusk County · bound for
- Accidents and incidents in Texas 6,244 since 1982 · 1,061 in the last ten years
- Texas 29,986 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN25LA096.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.
