DEN07IA021 · Beech P35
Beech P35 and Beech K35 · Incident: midair collision during landing
Event
- NTSB case
- DEN07IA021
- 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
- Incident
- 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
- Unknown
- 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 · Beech P35
- Aircraft type
- Beechcraft 35
- 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
- N102H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 00V · Peyton, COTo Los Alamos Airport (LAM), Los Alamos, 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 · flare/touchdown
- 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
- Minor
Aircraft 2 · Beech K35
- Aircraft type
- Beechcraft 35
- 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
- N5368E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yerington Municipal Airport (O43), Yerington, NVTo Los Alamos Airport (LAM), Los Alamos, 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 · flare/touchdown
- 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
- Minor
Cause areas
- Pilot in command › Visual lookout, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane, a Beech P35, approached the airport from the north. At a local reporting location for airport, the pilot reported on the common traffic advisory (CTAF) frequency, 123.0 MHz, his position, altitude, and intention to land. The pilot completed his pre-landing checks approximately 1/2 miles from the runway 27 threshold and did not note any other aircraft or objects on the runway. Approximately 10 feet above the runway, the pilot began to initiate his landing flare when he heard a "clunk" sound. The airplane began what the pilot thought was his landing roll; however, his airplane was still 6 to 7 feet above the runway. The pilot then noticed his airplane begin to turn to the right and he attempted to correct to the left. Subsequently, the pilot observed another airplane underneath his airplane. Both airplanes turned to the right and came to rest on the runway. The pilot did not receive any transmissions from other aircraft in the area at the time of his approach and landing. The pilot of the other airplane, a Beech K35, reported that while en route with flight following from air traffic control, he and his passenger reviewed the airport chart because it was an "unfamiliar airport." The Beech K35 also approached the airport from the north, and he reported his position, altitude and intentions on the frequency 122.8 MHz. During the approach, the pilot and passenger did not hear over the radio or see any other aircraft in the area. The Beech K35 airplane entered a right base for runway 27 at 8,000 feet mean sea level. The pilot landed the airplane on runway 27 and approximately one second after touchdown, the Beech P35 airplane landed on top of his airplane. The CTAF for the airport is 123.0 MHz.
Probable cause
the failure of both pilots to maintain adequate visual lookout during the visual approach. A contributing factor was the failure of the N5368E's pilot to communicate his intentions on the Common Traffic Advisory Frequency.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07IA021
- Event ID
- 20061108X01625
- Case number
- DEN07IA021
- 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, coordinates. 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: 39b56aaf93d5b0eef65de07f200ae5ca1c608e577e3b66258fd518077ba4d3ba; retrieved 2026-09-22T04:15:23.265Z.