LAX84FA498 · Cessna 172Q
Embry Riddle Aero. Univ Cessna 172Q · Accident: in flight collision with object en route
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Prescott Regional Airport - Ernest A. Love Field (PRC)
Event
- NTSB case
- LAX84FA498
- 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 172Q
- 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
- N915ER
- Operator
- Embry-Riddle Aero. Univ
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZ
- 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
- En route · descent
- 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(cfi) › Diverted attention
- Pilot in command(cfi) › Level off, delayed
- Pilot in command(cfi) › Proper altitude, not maintained
- Pilot in command(cfi) › Visual lookout, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A DESCENT TO THE 5,042 FT ELEVATION ARPT THE ACFT IMPACTED THE TREES AND MOUNTAINOUS TERRAIN AT THE 7,000 FT LEVEL. ACCORDING TO THE PILOT, WITH THE HOODED STUDENT PILOT AT THE CONTROLS, THE FLIGHT BEGAN IT'S DESCENT FROM 10,500 FT 30 MILES FROM THE ARPT. DURING THE DESCENT THE LOCAL ALTIMETER SETTING WAS DIALED IN AND THE CFI REALIZED THE ACFT WAS TOO LOW. A CLIMB WAS CALLED FOR AND THE TREES WERE SEEN JUST PRIOR TO IMPACT. THE CFI STATED THAT THEY HAD BEEN WORKING ON VOR INTERCEPTS DURING THE DESCENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX84FA498
- Event ID
- 20001214X41106
- Case number
- LAX84FA498
- 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: 0e6a89584069c9d54f8c0e58d792e752552da4722fe5d9db4c60c6f5165e5d05; retrieved 2026-09-22T02:05:55.149Z.