CEN14FA522 · Cessna T337G
Cessna T337G · Accident: controlled flight into terrain/object (CFIT) en route
From Litchfield Municipal Airport (3LF) to Aurora Municipal Airport (ARR)
Event
- NTSB case
- CEN14FA522
- 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 T337G
- 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
- N37E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Litchfield Municipal Airport (3LF), Litchfield, ILTo Aurora Municipal Airport (ARR), Sugar Grove, IL
- Aircraft age
- About 41 years (built 1973)
- 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 · descent
- Defining eventThe 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
- Controlled flight into terrain/object (CFIT)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was approaching the destination airport at the conclusion of a cross-country flight in dark night, visual meteorological conditions. According to radar track data, the pilot had maintained a gradual descent profile during the final 7 minutes of the flight. About a minute before the accident, during a routine conversation, the tower controller at the destination airport told the pilot that he saw the airplane on radar at 1,800 ft mean sea level (msl). At that time, the airplane was about 1,200 ft above the ground and descending. The airplane subsequently collided with trees located along a ridge at an elevation of about 645 ft msl. The destination airport was located at 712 ft msl. According to radar track and engine monitoring data, the pilot did not attempt to slow the airplane's descent before the accident. A postaccident examination of the airplane and flight instruments did not reveal any anomalies that would have precluded normal operation during the accident flight. Additionally, the pilot had selected a Kollsman window setting that would have minimized any altimeter indication errors.
The 80-year-old pilot had moderate-to-severe coronary artery disease, which can result in a sudden loss of consciousness; however, based on available radar track data and his communications with the airport tower controller, it is unlikely that his coronary artery disease contributed to the accident. The pilot also had longstanding, open-angle glaucoma, which had required a series of medical and surgical treatments over the years, and cataracts in both eyes. The cataract in the left eye had been removed in 2008, but the cataract in the right eye had recently increased in size. An ophthalmology evaluation in the weeks before the accident noted a significant increase in the size of a central scotoma (blind spot) related to longstanding glaucoma in the left eye, and declining corrected distant visual acuity bilaterally. Although the pilot met the Federal Aviation Administration medical certification standard of 20/40 vision in daylight conditions, the glaucoma and cataract likely impaired his night vision and, as such, impeded his ability to judge altitude using available visual cues in dark nighttime conditions. Additionally, toxicology testing identified diphenhydramine, a sedating antihistamine, in the pilot's blood at therapeutic levels. Research has shown that the use of diphenhydramine can impair cognitive and psychomotor performance. The pilot's failure to identify the airplane's low altitude during cruise descent further supports that he was likely impaired by the use of diphenhydramine.
Probable cause
The pilot’s failure to recognize the airplane’s low altitude and arrest the airplane’s descent on approach to the airport in dark night conditions, which resulted in controlled flight into terrain. Contributing to the accident was the pilot’s degraded night vision due to glaucoma and a cataract and his impairment from the use of diphenhydramine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14FA522
- Event ID
- 20140929X12854
- Case number
- CEN14FA522
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-09-29.
- API snapshot SHA-256: 7d52d9ada681092ed82453b8fa840fb81595909f4a6d8a7e1043630153083250; retrieved 2026-09-14T17:26:51.795Z.