NYC93FA013 · Cessna 195
Cessna 195 · Accident: loss of control in flight en route
From Deck Airport (9D4) to Greater Binghamton/Edwin A Link field (BGM)
Event
- NTSB case
- NYC93FA013
- 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
- 1 · 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
Cessna 195
- Aircraft type
- Cessna 195
- 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
- N4308V
- Operator
- Herbert A. Schaffner · private individual
- Onboard fatalities
- Unknown
- Route
- From Deck Airport (9D4), Myerstown, PATo Greater Binghamton/Edwin A Link field (BGM), Binghamton, 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
- En route · cruise
- 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
- 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
- Pilot in command › Aircraft control, uncontrolled
- Pilot in command › Incapacitation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
RADAR DATA SHOWED THE AIRPLANE IN A CLIMB TO 7800 FT, LEVEL AT 7700 FT FOR APPROX 1 MINUTE, AND THEN ENTER A DESCENT. THE RADAR DATA WAS PUT INTO A COMPUTER PROGRAM WHICH SHOWED THAT THE HIGHEST VERTICAL SPEED RECORDED WAS 19,000 FPM, WITH A TAS OF 279.9 KTS (321.9 MPH). EVIDENCE OF FLUTTER WAS FOUND ON THE ELEVATOR, WHICH SEPARATED FROM THE HORIZONTAL STABILIZERS, AND THE WINGS HAD FAILED SYMMETRICALLY IN NEGATIVE LOADING. THE PILOT HAD BEEN TAKING VASOTEC FOR HYPERTENSION. DATA SUPPLIED FROM FLIGHT TESTING FOUND THAT IF THE AIRPLANE WAS TRIMMED FOR A CLIMB AT 112 MPH, AND THE POWER WAS NOT CHANGED, A 13 POUND FORWARD FORCE ON THE CONTROL WHEEL WOULD CAUSE THE AIRPLANE TO ACCELERATE TO 196 MPH. THE NEVER EXCEED SPEED FOR THE AIRPLANE IS 200 MPH.
Probable cause
A LOSS OF CONTROL DUE TO PILOT INCAPACITATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93FA013
- Event ID
- 20001211X15926
- Case number
- NYC93FA013
- 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: 5479c3b3a097e4b49f74309130162df176804b87688619503dbf6d5845e7b8d5; retrieved 2026-09-21T00:52:01.401Z.