FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC83LA008 · Cessna 172P

10 Oct 1982 · GRAHAMSVILLE, NY, United States

Cessna 172P · Accident: in flight collision with object while maneuvering

From Sullivan County International Airport (MSV) to Sullivan County International Airport (MSV)

Report a problem

Event

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

Cessna 172P

Aircraft type
Cessna 172
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
N54177
Onboard fatalities
Unknown
Route
From Sullivan County International Airport (MSV), Monticello, NYTo Sullivan County International Airport (MSV), Monticello, 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
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
Substantial

Cause areas

  • Pilot in command › Altitude, misjudged

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

NTSB narrative

THE PILOT AND TWO PASSENGERS DEPARTED ON A LOCAL SIGHTSEEING FLIGHT WITH FULL FUEL TANKS. ABOUT ONE HOUR AFTER TAKEOFF, THE PILOT FLEW OVER THE PASSENGERS' HOUSE TO TAKE PICTURES. WHILE A PASSENGER WAS PHOTOGRAPHING THE HOUSE, THE PILOT'S ATTENTION WAS DIVERTED TOWARD THE GROUND. DURING THIS TIME, HE LOST REFERENCE OF HIS ALTITUDE AND AIRSPEED AND BEGAN TO APPROACH RISING TERRAIN. HE APPLIED FULL POWER AND ATTEMPTED TO CLIMB, BUT THE PLANE WAS NEAR STALLING SPEED. SUBSEQUENTLY, THE LEFT WING CONTACTED TREE TOPS AND THE AIRCRAFT CARTWHEELED TO THE GROUND.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC83LA008
Event ID
20020917X05079
Case number
NYC83LA008
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: 186184fb7a7f2e3b4850877b039f2db38d4852849fe07c8aa7ba2c44b5834ba0; retrieved 2026-09-24T00:29:20.871Z.