BFO94FA073 · Beech B24R
Fort Bragg Flying Activity Beech B24R · Accident: hard landing
From Rocky Mount Wilson Regional Airport (RWI) to College Park Airport (CGS)
Event
- NTSB case
- BFO94FA073
- 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
- 4 · 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 B24R
- Aircraft type
- Beechcraft 24
- 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
- N9353S
- Operator
- Fort Bragg Flying Activity
- Onboard fatalities
- Unknown
- Route
- From Rocky Mount Wilson Regional Airport (RWI), Rocky Mount, NCTo College Park Airport (CGS)
- 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
- Landing · flare/touchdown
- First occurrenceThe 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
- Hard landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush
- 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
- Pilot in command › Flare, improper
- Pilot in command › Recovery from bounced landing, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a landing, the airplane bounced three times with its nose wheel contacting the runway before the main gear. After the third bounce, over 1/2 of the way down the 2,610-foot-long runway, the pilot initiated a climb. Witnesses stated that the airplane's flaps were extended during the aborted landing. Witnesses also stated that after the airplane started to climb, it went into a shallow left turn and climbed to about 50 feet AGL. During the climb the airplane stalled and impacted a 30-foot-high building located about 1/4 mile beyond the end of the runway. Post accident examination of the airframe revealed the flaps were retracted and the landing gear were extended. According to the Beechcraft Balked Landing Procedures, the landing gear should be retracted after full throttle is applied. The flaps should not be retracted until the airplane is clear of obstacles and trimmed for best rate-of- climb. No airframe or engine anomalies were noted. At the time of the accident the airplane was about 77.5 lbs. over its maximum allowable gross weight. Wind direction was reported to be 'extremely variable.'
Probable cause
the pilot's improper flare and delayed recovery from the bounced landing. Factors contributing to the accident were the pilot's failure to retract the landing gear during the aborted landing; the exceeded allowable gross weight; and the unfavorable wind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO94FA073
- Event ID
- 20001206X01040
- Case number
- BFO94FA073
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 6cccb5faafc26b6d0420d3c7854ec6f2d15ef819dca8ed5b7dbf5b5bd89dc095; retrieved 2026-09-21T00:10:58.683Z.