FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN84FA251 · Cessna R172E

6 Aug 1984 · Farmington, NM, United States

New Mexico State Police Cessna R172E · Accident: in flight collision with object while maneuvering

From Four Corners Regional Airport (FMN) to an unrecorded destination

Report a problem

Event

NTSB case
DEN84FA251
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
2 · 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
Government
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 R172E

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
N601SP
Onboard fatalities
Unknown
Route
From Four Corners Regional Airport (FMN), Farmington, NMTo 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
Public Aircraft
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
Wire, transmission
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 › Clearance, not maintained
  • Pilot in command › Low pass, performed
  • Pilot in command › Visual lookout, inadequate

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

NTSB narrative

AFTER BEING AIRBORNE 1 HOUR AND 10 MINUTES THE TRAFFIC SURVIELLANCE FLT WAS CANCELLED. THE PLT TRANSMITTED TO THE POLICEUNITS ON THE GROUND THAT HE WOULD 'BUZZ' THEM AS HE LEFT THE AREA. DURING THIS PASS THE ACFT STRUCK A HIGH VOLTAGE TRANSMISSION LINE 88.9 FT AGL. THE ACFT IMPACTED OUT OF CONTROL IN APRX 70 DEG ANGLE OF BANK 216 FT FROM THE WIRE- STRIKE. MOST OF THE WRECKAGE WAS CONSUMED BY POST CRASH FIRE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN84FA251
Event ID
20001214X40666
Case number
DEN84FA251
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: 0ffbfecb0393bcc71b87ed6f2ac68b506797309d17e68b82b57b33fe354e57b7; retrieved 2026-09-18T14:38:58.587Z.