NYC92FA050 · Beech A36
Beech A36 · Accident: in flight collision with object while maneuvering
Event
- NTSB case
- NYC92FA050
- 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
- 3 · 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N236JS
- Operator
- John E. Schweller · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Maneuvering
- 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 object
- 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
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Copilot/second pilot › Altitude, inadequate
- Pilot in command › Altitude, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS ON A LOCAL NIGHT FLIGHT TO SEE THE XMAS LIGHTS OF DAYTON FROM THE AIR. A PAX STATED THAT WHEN SHE THOUGHT THEY WERE GOING TO LAND THE ACFT HIT TREES. THERE WAS NO UNUSUAL ENGINE SOUND, OR ANYTHING DIFFERENT FROM OTHER FLIGHTS. THE ACCIDENT OCCURED ABOUT 1 MI FROM THE AIRPORT. THE LEFT SEAT PILOT WAS NOT INSTRUMENT-RATED. THE RIGHT SEAT PILOT WAS THE ACFT OWNER, AND WAS INSTRUMENT RATED. THE PILOT OPERATING THE CONTROLS AT THE TIME OF THE ACCIDENT WAS NOT DETERMINED. THERE ARE NO FAA-APPROVED APPROACHES FOR THE ARPT; HOWEVER, THE OWNER HAD DESIGNED A LORAN-C APPROACH AND TWO R-NAV APPROACHES FOR PERSONAL USE. THE ACTIVE WAYPOINT FOUND IN THE ACFT'S LORAN UNIT COINCIDED WITH THE ARPT. THE OWNER WAS DESCRIBED AS A PERSON WHO ' WAS PROUD OF, AND WOULD BE EAGER TO SHOW OTHER PILOTS FLYING THE AIRPLANE, THE PROCEDURES FOR USE OF THE EQUIPMENT INSTALLED.'
Probable cause
THE FAILURE OF THE PILOTS TO MAINTAIN ADEQUATE TERRAIN CLEARANCE. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE: THE NIGHT CONDITIONS, REDUCED VISIBILITY DUE TO FOG, AND THE LIKELIHOOD THAT THE PILOTS DIVERTED THEIR ATTENTION TO THE OPERATION OF THE LORAN EQUIPMENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92FA050
- Event ID
- 20001212X18651
- Case number
- NYC92FA050
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1991-12-26.
- API snapshot SHA-256: bb1d14d7cee96cfdec826004a7478f34c56784d76b53baf748bddbde8a88e5a7; retrieved 2026-09-21T01:26:04.450Z.