FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC98FA185 · Cessna 170A

12 Sept 1998 · LAGRANGEVILLE, NY, United States

Cessna 170A · Accident: loss of control in flight during takeoff

From 44N to N77 · Mahopac, NY

Report a problem

Event

NTSB case
NYC98FA185
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 170A

Aircraft type
Cessna 170
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
N4709Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From 44NTo N77 · Mahopac, 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
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
Loss of control in flight
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/spin
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 › Airspeed, inadequate
  • Pilot in command › Stall/spin, inadvertent

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the initial climb after takeoff, the airplane was observed climbing at a steep pitch angle. The airplane's wings rocked back and forth a few times, and then it rolled and dropped to the right. Witnesses described the engine noise as loud and constant until the point of impact. The airplane came to rest inverted in a wooded area about 1,600 feet beyond the approach end, 110 feet to the right of, and at an elevation 40 feet below the departure runway. Examination of the airframe and engine did not reveal any pre-impact mechanical malfunctions.

Probable cause

The pilot's failure to maintain airspeed during the takeoff, which resulted in an inadvertent stall/spin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC98FA185
Event ID
20001211X11146
Case number
NYC98FA185
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: f404f6887f76996b7572c132ee137e20509120396d7bec69a84ac0f6a9fc7cce; retrieved 2026-09-20T22:26:28.545Z.