Bellanca 7GCBC accident near Bonilla, South Dakota, October 10, 2025
On October 10, 2025 at about 11:45 pm local time, a 1976 Bellanca 7GCBC, registered N53853, was substantially damaged in an accident during landing (flare/touchdown) near Bonilla, South Dakota (Na airport). 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).
The NTSB's probable cause their words, unchanged
The pilot’s inadequate flight planning and his failure to maintain aircraft control during the precautionary off-airport landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 10, 2025 · about 11:45 pm local time · cases in 2025
- Place
- Bonilla, South Dakota · Na · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Bellanca 7GCBC, built 1976 · all 7GCBCs on the register
- Registration
- N53853 · registry record · serial 908-76
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was conducting a personal flight when he realized that he would not be able to return to his private airstrip before sunset. The pilot decided to make a precautionary landing in a harvested soybean field. The pilot stated that the selected field was hillier than it appeared from altitude, and the airplane bounced upon touchdown, the propeller struck the ground, and during the sudden deceleration the airplane nosed over in the field. The airplane sustained substantial damage to both wings, vertical stabilizer, and the rudder. The pilot did not report any preimpact mechanical malfunctions or failures that would have precluded normal operation of the airplane.
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
- Off-field or emergency landing during landing (landing roll)
- Hard landing during landing (flare/touchdown) defining event
- Loss of control on ground during landing
- Nose over/nose down during landing
The NTSB's findings
- Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Pilot
- Environmental issues › Conditions/weather/phenomena › Light condition › (general) › Decision related to condition
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Physical environment › Terrain › Rough terrain › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 352.8 hours in all; 145.6 in this make and model; 9.1 in the last 90 days; 4.9 in the last 30 days; 352.8 as pilot in command
- Last flight review: May 28, 2020
- Medical certificate: Sport Pilot
- Seat: frt
- Injury: minor injuries
The aircraft
- Airframe total time: 2,507 hours
- Last inspection: annual inspection, July 28, 2025
- Maximum gross weight: 1,650 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320-A2B (piston); 1,355 hours total
The flight
- Departed from: PVT Tulare SD at 10:45 pm
- Destination: PVT Tulare SD
- Flight plan: none
Weather at the time
- Light: dusk
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 36°F (2°C)
- Altimeter: 30.19 inHg
- Observation at 5:55 pm from HON, 15 miles away
Weather report (METAR): METAR KHON 102255Z AUTO 00000KT 10SM CLR 21/02 A3019 RMK AO2 SLP227 T02060022=
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 1 picture from the NTSB's docket, as the NTSB released them
The 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
2 documents, released by the NTSB on January 15, 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 | Photos | PDF, 2 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N53853 the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N53853 on the register today · the tail number may have moved to another aircraft since
- Bellanca 7 Citabria 1,228 registered today · the model family and its accident history
- Bellanca 2,700 aircraft on the register
- Engine: Lycoming O-320-A2B 179 aircraft carry this series today · as the NTSB recorded it
- Accidents and incidents in South Dakota 469 since 1982 · 69 in the last ten years
- South Dakota 2,280 aircraft registered
- Other NTSB records under N53853 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN26LA019.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.
