NYC96LA069 · Bellanca 7KCAB
Bellanca 7KCAB · Accident: hard landing
From No airport to an unrecorded destination
Event
- NTSB case
- NYC96LA069
- 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
- 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
Bellanca 7KCAB
- Aircraft type
- Bellanca 7
- 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
- N7807S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From No airportTo not recorded
- 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
- 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
- Pilot in command › Directional control, not maintained
- Pilot in command › Flare, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had practiced two takeoffs and landings at his base airstrip, then departed the pattern and flew to another airstrip for five touch-and-go landings. He then flew back to his base airstrip and established the airplane on an approach to runway 29. The pilot stated that while on final approach, the airplane's angle of descent was low, and he added power to maintain altitude. After clearing the trees at the end of the runway, he then leveled the nose for a short field landing. The pilot stated that the airplane did not respond and he 'pulled the stick full aft and made a hard landing.' After landing, the airplane veered right, and the right wing struck trees along the side of the runway. The pilot estimated that the winds were from 300 degrees at 22 knots, gusting to 25. The sod strip was about 4,000 feet long, 100 feet wide, and surrounded by 75-foot high trees on all sides.
Probable cause
the pilot's improper flare and failure to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA069
- Event ID
- 20001208X05470
- Case number
- NYC96LA069
- 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: b210287c049497cc59a69ce629cf9ec888593a5955db2592df618ccdb8923b60; retrieved 2026-09-22T22:47:05.029Z.