FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12CA520 · Fleet FLEET 16B

18 Aug 2012 · Bayport, NY, United States

Fleet FLEET 16B · Accident: hard landing

From Bayport Aerodrome (23N) to Bayport Aerodrome (23N)

Report a problem

Event

NTSB case
ERA12CA520
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
Visual Meteorological Cond

Fleet FLEET 16B

Aircraft type
Fleet 16
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
N343SF
Onboard fatalities
Unknown
Route
From Bayport Aerodrome (23N), Bayport, NYTo Bayport Aerodrome (23N), Bayport, 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
Landing
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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that he returned to the departure airport after a brief local flight and entered the traffic pattern. While on final approach to the runway, he initiated a slip to the left to descend and increase his visibility of the runway. The pilot stated that during previous flights in the tailwheel-equipped biplane, after he exited the slip just before touchdown, the airplane would "float" down the runway in ground effect. However, when he exited the slip during the accident flight, the rate of descent remained constant, and the airplane's contact with the runway was "fairly severe." The landing gear subsequently collapsed, and the airplane departed the right side of the runway and nosed over, resulting in substantial damage to the right upper wing. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation, and that the accident could have been prevented by a "quicker reaction" and "increasing [engine] power to arrest descent rate."

Probable cause

The pilot’s improper landing flare, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12CA520
Event ID
20120821X34711
Case number
ERA12CA520
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: 38770732504ff73ad2c03c4089f99179a8cd133c5fa37d8b90e9f5ed0e210afb; retrieved 2026-09-15T19:27:49.705Z.