FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC82FFA05 · Navion A

16 May 1982 · Hancock, NY, United States

Navion A · Accident: in flight collision with terrain/water during initial climb

From Hancock, NY to Danbury, CT

Report a problem

Event

NTSB case
NYC82FFA05
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

Navion A

Aircraft type
Navion A
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
N91662
Operator
Joseph J. Schnider · private individual
Onboard fatalities
Unknown
Route
From Hancock, NYTo Danbury, CT
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
Initial climb
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
In flight collision with terrain/water
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

  • Hydraulic system › Undetermined

Approximate · Estimated position: the centre of Hancock, NY, the place the record names. Not the accident site.

NTSB narrative

THE PILOT REPORTED THAT DURING TAKEOFF, HE CLIMBED TO ABOUT 20 TO 30 FT AND RAISED THE GEAR. AT ABOUT THAT TIME, THE AIRCRAFT BEGAN TO SINK. HE STATED THAT HE PULLED THE POWER OFF JUST BEFORE THE AIRCRAFT HIT THE GROUND A FEW MILES FROM THE AIRPORT. AN INVESTIGATION REVEALED THAT THE FLAPS WERE NOT DAMAGED, AS IF THEY WERE NOT EXTENDED DURING IMPACT. HOWEVER, THE FLAP CONTROL WAS FOUND IN THE DOWN POSITION. THE FLAPS WERE FOUND ABOUT 20 DEG DOWN AND THE FLAP INDICATOR WAS INDICATING ABOUT 1/3 DOWN. THE INVESTIGATOR CAPPED OFF A BROKEN LANDING GEAR HYDRAULIC LINE AND FILLED THE HYDRAULIC RESERVOIR, BUT THE HAND PUMP WOULD NOT OPERATE DUE TO AIR IN THE SYSTEM THE ENGINE WAS THEN RUN, AND AFTER THAT, THE HYDRAULIC SYSTEM OPERATED NORMALLY. THE PILOT SUSPECTED THAT THE FLAPS CAME UP WHEN HE RAISED THE GEAR AFTER TAKEOFF. THIS AIRCRAFT WAS EQUIPPED WITH A FLAP SYSTEM THAT WAS TO BE SET EITHER FULL UP OF FULL DOWN. AN INTERMEDIATE SELECTION WOULD NOT INSURE A POSITIVE SELECTED POSITION.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC82FFA05
Event ID
20020917X04033
Case number
NYC82FFA05
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: 7ba9bc44cbf6719fe00a5f42a95882e1fd143952c41caeb92c7e93176ada1c5e; retrieved 2026-09-21T18:15:38.528Z.