NYC92LA158 · Stinson ST-75
Stinson ST-75 · Accident: loss of control on ground/water during landing
From Teterboro Airport (TEB) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC92LA158
- 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
Stinson ST-75 Possible conflict
- Aircraft type
- Stinson ST-75
- 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
- N8495K
- Operator
- Richard Kravit
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (TEB), TETERBORO, NJTo 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
- Landing · landing roll
- 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 on ground/water
- 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
- Object › Aircraft parked/standing
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Ground loop/swerve, inadvertent
Approximate · Estimated position: the centre of Sussex, NJ, the place the record names. Not the accident site.
NTSB narrative
DURING THE LANDING ROLL THE AIRPLANE BEGAN TO VEER TO THE LEFT OF THE RUNWAY CENTERLINE. THE PILOT ATTEMPTED TO CORRECT THE DEVIATION BY APPLYING RIGHT RUDDER AND RIGHT BRAKE, BUT WAS NOT SUCCESSFUL IN STOPPING THE AIRPLANE FROM DRIFTING TO THE LEFT. THE LEFT MAIN WHEEL WENT OFF THE RUNWAY PAVEMENT INTO SOFT, WET GROUND, WHICH RESULTED IN THE AIRPLANE GROUND LOOPING AND STRIKING TWO PARKED AIRPLANES.
Probable cause
THE PILOT FAILED TO MAINTAIN CONTROL OF THE AIRPLANE DURING THE LANDING ROLL, AND INADVERTENTLY SWERVED AND GROUND LOOPED INTO TWO PARKED AIRPLANES. A FACTOR IN THIS ACCIDENT WAS THE PILOT'S LACK OF EXPEREINCE IN THIS MAKE AND MODEL AIRPLANE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92LA158
- Event ID
- 20001211X15505
- Case number
- NYC92LA158
- 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: 897638636c3c2359b1d363029a86841e4d2f960962bdca3bb0341af2532d54ff; retrieved 2026-09-23T02:45:57.662Z.