NYC94LA152 · Aeronca 11AC
Aeronca 11AC · Accident: loss of control in flight on approach
From BO4 to BO4 · NY
Event
- NTSB case
- NYC94LA152
- 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
Aeronca 11AC
- Aircraft type
- Aeronca 11
- 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
- N3441E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From BO4To BO4 · 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
- 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
- Loss of control in flight
- 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
- Substantial
Cause areas
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLOAT-EQUIPPED AIRPLANE, AFTER A GO AROUND WAS EXECUTED DUE TO TRAFFIC, WAS ON DOWNWIND LEG AT 500 FEET AGL AT AN AIRSPEED OF 70 TO 75 KNOTS. ACCORDING TO THE PILOT, WHILE ON DOWNWIND HE SENSED A SLIGHT SINKING SENSATION. HE ADVANCED THE THROTTLE AND RELAXED BACK PRESSURE ON THE CONTROL WHEEL. THE PILOT DID NOT REMEMBER DETAILS OF THE FLIGHT AFTERWARDS. THE PASSENGER ALSO REPORTED THE AIRPLANE BEGAN SINKING ON DOWNWIND AND THAT HE ALONG WITH THE PILOT PULLED ON THE CONTROL WHEEL, RAISING THE NOSE IN AN UNSUCCESSFUL ATTEMPT TO ARREST THE DESCENT. THE AIRPLANE SUBSEQUENTLY STRUCK THE GROUND. THE LANDING WAS TO BE DONE TO THE NORTHEAST ON THE HUDSON RIVER INTO A 6 KNOT WIND. THE DOWNWIND WAS FLOWN OVER LAND, PARALLEL TO THE SHORELINE. THE EXAMINATION OF THE AIRPLANE REVEALED NO MECHANICAL MALFUNCTIONS. THE PILOT REPORTED THE WINDS WERE FROM THE NORTHEAST AT 6 KNOTS.
Probable cause
the pilots failure to maintain adequate airspeed, which resulted in a stall/mush.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC94LA152
- Event ID
- 20001206X02125
- Case number
- NYC94LA152
- 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: cee186862a172d6295bea3d7704066a2374427b05f990653134ec1e9749714cc; retrieved 2026-09-21T13:42:55.038Z.