NYC87FA023 · Cessna R172K
Cessna R172K · Accident: in flight collision with object while maneuvering
From an unrecorded airport to COX · Maryville, TN
Event
- NTSB case
- NYC87FA023
- 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 R172K
- 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
- N7526V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo COX · Maryville, TN
- 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
- Pilot in command › Altitude, misjudged
- Pilot in command › Altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT WAS OBSERVED DEPARTING AT APPROX 2010 HOURS, REVERSING COURSE AND FLYING OVER THE AIRPORT AT 300-400 FT AGL. THE AIRCRAFT CRASHED 3/4 MILES SOUTH OF THE AIRPORT IN UNPOPULATED, MOUNTAINOUS/HILLY TERRAIN AT AN ELEVATION OF 1560 FEET, WHICH IS 104 FEET LOWER THAN THE AIRPORT ELEVATION. THE WRECKAGE WAS FOUND APPROX 2 DAYS LATER. THE PILOT, THE SOLE OCCUPANT, WAS FATALLY INJURED. THE AIRCRAFT WAS DESTROYED. THERE WAS NO FIRE. RECORDS INDICATE THAT THE PILOT HAD 6.1 HOURS OF NIGHT TIME, WITH LAST NIGHT FLIGHT BEING 23 MONTHS PRIOR TO THE ACCIDENT. A TOTAL OF 155 HOURS FLYING TIME WAS ACCUMULATED OVER A 9 YEAR AND 2 MONTH PERIOD. THERE WAS NO EVIDENCE OF MALFUNCTION WITH THE AIRCRAFT OR RELATED EQUIPMENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC87FA023
- Event ID
- 20001213X35044
- Case number
- NYC87FA023
- 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 1986-10-20.
- API snapshot SHA-256: 00a70b5f00ba1e81b52d715743e6f414f6a53e369e5c4e854987ac6a1de2b209; retrieved 2026-09-21T04:21:53.315Z.