FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN07FA100 · Beech 58

16 Jun 2007 · Placitas, NM, United States

Beech 58 · Accident: in flight collision with terrain/water en route

From Zamperini Field (TOA) to Clinton Sherman Airport (CSM)

Report a problem

Event

NTSB case
DEN07FA100
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
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

Beech 58

Aircraft type
Beechcraft 58
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
N6750R
Operator
Robert P. Iacono · private individual
Onboard fatalities
Unknown
Route
From Zamperini Field (TOA), Torrance, CATo Clinton Sherman Airport (CSM), Clinton, OK
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 · cruise
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 terrain/water
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

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Approximately three and one half hours into the cross country flight, the airplane impacted mountainous terrain during daylight hours in visual meteorological conditions. No pre-impact engine or airframe anomalies, that would preclude normal operation prior to impact, were identified. Radar data and examination of the accident site indicated that the airplane was in level flight at a constant airspeed prior to impact with terrain. Toxicology testing of the pilot's muscle and liver specimens revealed the presence of 5 different medications used for the treatment of mental disorders. The pilot, a neurosurgeon, indicated no medications or medical conditions on his last application for airman medical certificate less than two months prior to the accident. That application noted that the pilot's medical license had been revoked.

Probable cause

the failure of the pilot to maintain adequate terrain separation, for undetermined reasons, which resulted in controlled flight into terrain. A contributing factor was the mountainous terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN07FA100
Event ID
20070628X00826
Case number
DEN07FA100
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: c861a50a2248aa1ba03f8aa31a35f1fa36d2b20a23c31ec438d31af06941affb; retrieved 2026-09-20T16:33:02.245Z.