Beech F35 accident near Ravenna, Texas, July 5, 2020
On July 5, 2020 at about 3:00 am local time, a 1955 Beech F35, registered N4219B, was substantially damaged in an accident during maneuvering near Ravenna, Texas. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Electrical and engine problems for reasons that could not be determined based on available evidence.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 5, 2020 · about 3:00 am local time · cases in 2020
- Place
- Ravenna, Texas · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries; 1 other was unhurt.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech F35, built 1955 · all F35s on the register
- Registration
- N4219B · no longer on the register · serial D-4180
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
While in cruise flight and after the pilot engaged the autopilot, a portable air conditioning unit was plugged into the airplane’s electrical system. When the unit was plugged into the system, the pilot heard a loud noise like a “firecracker” from the engine compartment, and the autopilot disengaged. The pilot ran the emergency checklist for an electrical failure and noticed a drop in engine rpm. Attempts to rectify the electrical issue and regain engine rpms were unsuccessful. The pilot located a private 3,000 ft grass airstrip to land on. As he approached the airstrip, he noticed a stack of large round hay bales on the edge of the runway. The pilot felt that trying to pull up over the bales would induce a stall, so he turned to the right just as the airplane touched down. About 100 ft after the airplane touched down, the left wing impacted the hay bales, which caused the airplane to spin left and come to a sudden stop. The airplane sustained substantial damage to the left wing. A postaccident examination of the airplane electrical systems did not determine the reasons for the reported electrical problems. The examination of the engine revealed that it was poorly maintained; however, it was not clear if this condition resulted in the loss of engine rpm or if the loss in rpm was related to the electrical system.
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
- Collision during takeoff/land during landing
- Electrical system malf/failure during maneuvering defining event
- Loss of engine power (partial) during maneuvering
The NTSB's findings
- Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Aircraft › Aircraft systems › Electrical power system › (general) › Not specified other cases naming the electrical power
- Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Not specified other cases naming the engine
Pilot
- Certificate: private
- Ratings: single-engine land
- Medical certificate: Unknown
- Seat: left
- Injury: minor injuries
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,775 lb
- Seats: 4
- Landing gear: retractable
- Engine: Continental E-225-8 (piston); 0 hours total
The flight
- Departed from: HHW Hugo OK
- Flight plan: none
- A second pilot was aboard
Weather at the time
- Light: night
- Wind: from 120° at 8 knots
- Visibility: 10 statute miles
- Sky: a few clouds
- Temperature: 87°F (31°C), dew point 74°F (23°C)
- Altimeter: 29.19 inHg
- Observation at 9:53 pm from GYI, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 |
Photographs from the investigation 2 pictures 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
4 documents, released by the NTSB on February 25, 2022. 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 Statement | PDF, 2 pages | View Download |
| 2 | NTSB and Pilot Email Correspondence | PDF, 3 pages | View Download |
| 3 | Mechanic Statement | PDF, 1 page | View Download |
| 4 | Photo Array | 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.
Connections how this case links to the rest of the register
- N4219B: not on the register today · the record of its deregistration
- Beechcraft F35 192 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Engine: Continental E-225-8 7 aircraft carry this series today · as the NTSB recorded it
- Sandy Creek Ranch Airport · nearest airport
- Stan Stamper Municipal · departed from
- Accidents and incidents in Texas 6,244 since 1982 · 1,061 in the last ten years
- Texas 29,992 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN20LA262.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.


