DEN07FA022 · Cessna 337C
Cessna 337C · Accident: loss of control on ground/water during landing
From Fort Worth Spinks Airport (FWS) to Alamogordo White Sands Regional Airport (ALM)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DEN07FA022
- 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
Cessna 337C Possible conflict
- Aircraft type
- Cessna 337
- 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
- N2500S
- Operator
- Thomas E. Cross, Sr · private individual
- Onboard fatalities
- Unknown
- Route
- From Fort Worth Spinks Airport (FWS), Fort Worth, TXTo Alamogordo White Sands Regional Airport (ALM), Alamogordo, 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
- Loss of control on ground/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 › Aircraft control, not possible
- Pilot in command › Incapacitation(cardiovascular)
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A witness to the accident said the airplane touched down on runway 21, then suddenly veered to the right. It went off the runway, crossed the median and parallel taxiway, across the parking ramp, and collided with a hangar "at a high rate of speed." A sign, a pickup truck parked outside, and an airplane inside the hangar were also damaged. After the collision, the rear engine continued to run at full power. The witness drove to the accident site and tried to gain access to the cockpit from outside the airplane in an attempt to shut the engine down. When this failed, he went inside the hangar, and tried to reach inside the cockpit. The engine quit running shortly thereafter. Another witness said he heard the airplane's engines running at "full throttle" and saw the airplane "hopping and fishtailing" across the ground. When he arrived at the accident site, the rear propeller was striking a blue-colored pickup truck parked next to the hangar, and oil was "spraying everywhere." The engine eventually shut down, and the propeller moved to the feathered position. The airplane was pulled from the hangar and examined. No discrepancies were noted with the steering and brake systems. According to the pilot's autopsy report, the pathologist found "focal, severe hardening (atherosclerosis) of the aorta within the abdomen. The heart showed changes (fibrosis) consistent with a previous ischemic episode (heart attack)." The pathologist opined, "Given the severity of hardening of the coronary arteries of the heart, it is possible that the decedent was in the early stages of a heart attack (coronary artery insufficiency). Changes of ischemia (impaired blood flow) in the heart muscle often take hours to become evident under the microscope; therefore, the decedent may have experienced some decrease blood flow to the heart without microscopic evidence at autopsy. Decreased blood flow due to coronary insufficiency can cause irregular heartbeat and/or unconsciousness rapidly." Toxicology protocol was performed by FAA's Civil Aeromedical Institute (CAMI) in Oklahoma City, Oklahoma. According to their report, diltiazem was present in the blood and liver. According to the Kaiser Permanente Drug Encyclopedia, diltiazem is a calcium channel blocker, and is used to treat high blood pressure (hypertension) and chest pain (angina). It may also be used to treat an irregular heartbeat.
Probable cause
The pilot's incapacitation due to a heart attack while landing, which resulted in a loss of control and an on ground collision with objects.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN07FA022
- Event ID
- 20061113X01637
- Case number
- DEN07FA022
- 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: 2cb428dfe6525697d66b080958ccbc1bbe9fd7f83a1ee7b88d3ec08d5dc77c9e; retrieved 2026-09-20T16:59:51.158Z.