ERA25FA103 · Beech V35B
Beech V35B · Accident: loss of engine power (total) en route
From Richmond County Airport (RCZ) to Carroll County Regional Jack B Poage Field (DMW)
Event
- NTSB case
- ERA25FA103
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech V35B
- Aircraft type
- Beechcraft 35
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2UZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Richmond County Airport (RCZ), Rockingham, NCTo Carroll County Regional Jack B Poage Field (DMW), Westminster, MD
- Aircraft age
- About 48 years (built 1977)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On January 25, 2025, about 1235 eastern standard time, a Beech V35B, N2UZ, was destroyed when it was involved in an accident near Charlottesville, Virginia. The airline transport pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to preliminary Federal Aviation Administration air traffic control communication data, the pilot made radio contact with the Charlottesville-Albemarle Airport (CHO) control tower at 1230. He declared an emergency and stated that the airplane was 10 miles south of the airport, at 5,500 ft mean sea level, and had experienced a total loss of engine power. The controller acknowledged the information and offered runway 3 to the pilot; however, at 1233, the pilot reported that the airplane was 3 to 4 miles south of the airport, and he was not going to be able to glide the airplane to the airport. The pilot added that he was going to try to land in a field south of the airport. The pilot subsequently stated that he was attempting to land in a field near a river, and the controller replied that he would send first responders to that location. No further communications were received from the accident airplane.
Review of Automatic Dependent Surveillance-Broadcast (ADS-B) data revealed that the airplane approached the approximate 1,800-ft-long field about 100 knots on a magnetic course about 310°. The airplane overflew the field and collided with trees at the end.
A debris path was observed at the end of the snow-covered field, which began with a portion of the inboard left wing and its fuel bladder, imbedded in a tree about 3 ft above the ground. The debris path extended about 175 ft on a magnetic course of 310°. An outboard section of left wing was located about 40 ft along the debris path, followed by the first ground scar 20 ft beyond that. Near the ground scar, outboard sections of both wings were identified. A section of wing was suspended in a tree and was also near the first ground scar, and the left main landing gear was located 20 ft beyond the ground scar. The main wreckage came to rest at the end of the debris path, inverted, and oriented on a north heading.
A postcrash fire consumed a majority of the main wreckage. Although the left main landing gear separated, the right main landing gear remained parallel to the right wing spar, consistent with a gear retracted position. Additionally, the nose landing gear remained attached to the fuselage, inside the gear well. A flap actuator was recovered, and measurement of its arm corresponded to a flaps position of between 0 and 5°. Measurement of the elevator trim actuator corresponded to a 5° tab down (nose-up) position.
The engine was recovered to a storage facility and examined. The propeller remained attached to the engine. All three propeller blades remained attached to the hub and did not exhibit rotational damage. The No. 2 cylinder exhibited impact damage, and the No. 4 cylinder valve cover was melted. The propeller would not rotate by hand. It was noted that only one of the three nuts remained that secured the oil filter mount. The mount was loose against the housing and the other two nuts were not located. The oil sump was subsequently removed to facilitate borescope examination, and only residual oil remained. A crack in the engine case was observed near the camshaft gear. Borescope examination revealed multiple metal fragments near a crankshaft counterweight. Additionally, metal fragments were found in the oil sump and oil filter element.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA25FA103
- Event ID
- 20250125199596
- Case number
- ERA25FA103
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: bb80d516bc0f7ebbd95db0729b995a6d7d507e3f94108c9d30a52834c8a68dc5; retrieved 2026-09-15T09:01:50.069Z.