FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI06FA037 · Piper PA-28-140

27 Nov 2005 · Atlanta, NE, United States

Piper PA-28-140 · Accident: in flight collision with object en route

From Centennial Airport (APA) to Morris Municipal Airport James R. Washburn field (C09)

Report a problem

Event

NTSB case
CHI06FA037
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
3 · 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
Instrument Meteorological Cond

Piper PA-28-140

Aircraft type
Piper PA-28
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
N5596F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Centennial Airport (APA), Denver, COTo Morris Municipal Airport James R. Washburn field (C09), Morris, IL
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 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
Tower (marked)
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
  • Pilot in command › Flight into adverse weather, continued

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, piloted by a non-instrument rated private pilot, was destroyed when it impacted a radio and television tower during cruise and subsequent impact with terrain. Visual to instrument meteorological conditions prevailed at the time of the accident. No flight plan was on file. Two witnesses saw the airplane flying eastbound and saw the airplane impact the tower. About 10 minutes prior to the accident, the tower site manager inspected the tower for the approaching snow and found the tower's lights operational. The tower was depicted on the sectional aeronautical chart. Weather about 250 degrees magnetic and 53 nautical miles from the accident site, weather was: Wind 360 degrees 23 knots gusting to 33 knots, visibility 10 statute miles: sky condition scattered 1,400 feet, overcast 2,500 feet; temperature 2 degrees C; dew point -1 degree C; altimeter 29.33 inches of mercury; remarks peak wind 350 degrees at 33 knots at 1051 and weather about 45 degrees magnetic and 7 nautical miles from the accident site, weather was: Wind 360 degrees at 19 knots gusting to 24 knots; visibility 10 statute miles; sky condition overcast 900 feet; temperature 1 degree C; dew point -1 degree C; altimeter 29.32 inches of mercury. The airplane fuselage came to rest inverted. The tower was found on the ground folded upon itself in an accordion shape. The airplane fuselage was about one tenth of a mile from the base of the antenna on a 101-degree magnetic heading. The wings were found separated from the fuselage in a debris field that, measured from the antenna base, extended southward about three tenths of a mile on about a 171 degree heading. An on-scene investigation revealed no pre-impact anomalies. Flight control continuity was established and all breaks in control cables were consistent with overload. Engine controls were checked and continuity was established. The airspeed indicator's needle was trapped at an indication of 120 mph. The fuel selector was found in a detent and a liquid that smelled like aviation gasoline was found in the fuel selector valve. The propeller exhibited leading edge nicks and gouges. The color of a media transfer on the propeller was consistent with the aviation orange paint on the tower. The right wing exhibited a rearward semicircular crush about the outer third of the wing's leading edge. The right horizontal stabilator was torn from the empennage and the stabilator exhibited a semicircular rearward crush at its root. The trim tab for the left horizontal stabilator was torn about its midspan and the torn section remained attached to the right horizontal stabilator trim tab. The separations of the left and right wings were consistent with overload. The bottom skin of the left wing exhibited linear tearing from its leading edge to its flap about three feet outboard of its wing root. A global positioning system was installed in the airplane.

Probable cause

The non-instrument rated private pilot not maintaining clearance from the marked tower and his continued flight into adverse weather during cruise flight. Factors were the marked tower and the low ceilings present at the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI06FA037
Event ID
20051206X01932
Case number
CHI06FA037
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: 2ba76dc28aae3f4e0bdd287f2038c22e207a74347b44c4cc0c5bd7e78627e1e7; retrieved 2026-09-20T17:44:28.147Z.