DEN99LA067 · Cessna 172I
Cessna 172I and Adventure Aviation Cessna 172N · Accident: midair collision during landing
Event
- NTSB case
- DEN99LA067
- 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
Aircraft 1 · Cessna 172I
- 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
- N46204
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Las Cruces International Airport (LRU)To Q34 · Portales, NM
- 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
- Landing
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Cessna 172N
- 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
- N738UF
- Operator
- Adventure Aviation
- Onboard fatalities
- Unknown
- Route
- From Las Cruces International Airport (LRU)To 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
- 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
- Landing
- 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
- Midair collision
- 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 › Identification of aircraft visually, not attained
- Pilot in command › Visual lookout, not obtained/maintained
- Pilot of other aircraft › Identification of aircraft visually, not attained
- Pilot of other aircraft › Visual lookout, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
N46204 experienced an electrical failure shortly after takeoff, and the pilot returned for landing. Just prior to touching down on the runway, N46204 landed on top of N738UF. The pilot of N738UF was performing touch and go landings with his student, and had just touched down when N46204 landed on top of the right wing section. Witnesses reported that the pilot of N46204 requested assistance starting the airplane on the morning of the accident due to a low battery, and the aircraft was hand-propped. According to FAR Part 91.113 (b), 'When weather conditions permit... vigilance shall be maintained by each person operating an aircraft so as to see and avoid other aircraft.' In addition, according to FAR 91.113 (g), 'When two or more aircraft are approaching an airport for the purpose of landing, the aircraft at the lower altitude has the right-of-way, but it shall not take advantage of this rule to cut in front of another which is on final approach to land or to overtake that aircraft.'
Probable cause
The pilot of N46204's failure to maintain visual lookout and to identify the other aircraft visually during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN99LA067
- Event ID
- 20001205X00455
- Case number
- DEN99LA067
- 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: 86ef5e8bd1e80f278aa330b2899ab362a47927b8161078c6dc2d6dc36619194f; retrieved 2026-09-22T15:24:32.183Z.