NYC06CA096 · Aeronca 7AC
Aeronca 7AC · Accident: forced landing
From Post Mills Airport (2B9) to Post Mills Airport (2B9)
Event
- NTSB case
- NYC06CA096
- 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
Aeronca 7AC
- Aircraft type
- Aeronca 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
- N82320
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Post Mills Airport (2B9), Post Mills, VTTo Post Mills Airport (2B9)
- 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 · emergency landing after takeoff
- 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
- Forced 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 › Preflight planning/preparation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During departure from runway 19, a 2,500-foot long, by 60-foot wide runway, the airplane "experienced difficulty climbing." When the flight instructor realized the airplane would not be able to clear trees at the end of the runway, he performed a forced landing to a field. During the landing, the airplane impacted a sign, resulting in substantial damage. The flight instructor reported no mechanical deficiencies with the airplane, and additionally stated that the wind conditions were "gusty" at the time of takeoff. He reported that the maximum gross weight of the airplane was 1,220 pounds, and the airplane weight at the time of the accident was 1,171 pounds. He stated the accident could have been prevented if "only one person was onboard the airplane, as the horsepower was marginal with two people onboard." He also stated that he should have been more aware of the changing wind conditions. The closest recorded weather observation, from an airport 27 miles to the northwest, included winds from 230 degrees at 11 knots, gusting to 21 knots.
Probable cause
The flight instructor's inadequate preflight planning, which resulted in a forced landing and subsequent impact with a sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06CA096
- Event ID
- 20060522X00595
- Case number
- NYC06CA096
- 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, coordinates. 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: 1cf636ac6104b6ad0422830d94a7d3e402d360b5b872f6660191a3322715913a; retrieved 2026-09-22T04:59:30.196Z.