ERA11CA309 · Beech A23
Beech A23 · Accident: controlled flight into terrain/object (CFIT) on approach
From Greene Airport (4N7) to Greene Airport (4N7)
Event
- NTSB case
- ERA11CA309
- 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
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
- Instrument Meteorological Cond
Beech A23
- Aircraft type
- Beechcraft 23
- 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
- N3548R
- Operator
- Gregory Arthur A
- Onboard fatalities
- Unknown
- Route
- From Greene Airport (4N7), Greene, NYTo Greene Airport (4N7), Greene, NY
- Aircraft age
- Not recorded
- 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
- Approach · VFR pattern final
- 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
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that while attempting to land in heavy rain and with low visibility, the airplane collided with trees to the right side of the runway before descending and impacting the runway. The collision damaged the left wing, collapsed the landing gear, and substantially damaged the engine firewall. The pilot did not report any mechanical malfunctions or failures with the airplane prior to the accident. Although the nearest weather observation facility reported no precipitation and 10-mile visibility, it was located 28 miles from the accident location.
Probable cause
The pilot's decision to continue a visual approach with low visibility and in heavy rain and his subsequent failure to maintain clearance from trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA309
- Event ID
- 20110524X22220
- Case number
- ERA11CA309
- 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. 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: b2727ce3e4c69d7edac55c6def2484fc30d86df5bdaef92d2c4e55f0709a56e1; retrieved 2026-09-15T16:12:10.258Z.