NTSB CAROL · Event
Event CHI05LA136
Registry · N4978T
FAA Aircraft Registry record.
Make / Model
CESSNA TR182
Year of manufacture
1981 · 24 years old at event
Engine
LYCOMING 0-540 SERIES (250 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19811105
ADS-B equipped
Yes — Mode-S A62D9B
Registrant of record
ROTH ROBERT A
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot failed to verify that the landing gear were fully extended and failed to perform the emergency landing gear extention procedures. Factors to the accident included the low hydraulic fluid level, and the weak battery that resulted in a partial electrical failure.
Factual narrative
On June 7, 2005, at 1545 central daylight time, a Cessna 182TR, N4978T, sustained substantial damage when the main landing gear collapsed during landing on runway 16 (5,000 feet by 150 feet, asphalt) at the Palwaukee Municipal Airport (PWK), Wheeling, Illinois. The commercial pilot was not injured. The 14 CFR Part 91 business flight departed Danville, Virginia, about 1135 eastern daylight time en route to PWK. Visual meteorological conditions prevailed at the time of the accident. The flight was on an instrument flight rules (IFR) flight plan. The pilot reported the airplane was at a cruise altitude of 20,000 feet for about 30 minutes when the attitude indicator failed. He continued to his destination without the attitude indicator and with the autopilot off. When he neared his destination, air traffic control (ATC) cleared the airplane to descend to 3,000 feet mean sea level. The pilot reported that he slowed the airplane to 110 kts. He reported that when he was 10 miles from the airport, he put in ten degrees of flaps and lowered the landing gear switch. He reported seeing a green light on the gear position indicator. He reported that the primary altimeter (electrically powered) was inoperative and was stuck at 2,900 feet. The pilot set 29.83 in the secondary altimeter's Kollsman window. He reported that ATC gave him radar vectors to intercept the localizer for landing on runway 16. ATC instructed the pilot to switch the radio frequency to PWK's tower frequency. The pilot reported that when he tried to contact PWK tower, he realized that the primary and secondary radios had failed. The pilot reported that he took out his hand-held radio and contacted PWK tower on it and reported to ATC that he had a radio failure. He reported that he realized that the airplane's HSI was inoperative and his portable Garmin 290 GPS had "turned itself off due to an interruption of electrical supply from the plane, due to the auto off feature when external power is discontinued." He turned the Garmin 290 back on and used the "direct to" feature to help him locate the airport. The pilot reported that he recognized that the airplane's GPS/radio/VOR receiver had powered down and was "recycling through the power-up check and was providing no radio or guidance information." The pilot reported: "As I descended to the runway, I pulled the power, added full flaps, and continued down the PAPI glideslope. Just prior to touchdown, I heard the controller comment that the wheels were not down. I pulled back on the yoke and saw that neither the amber nor green gear lights were on. As the plane was about to settle, I put the nose back down. I did not add power for a go around as it appeared that the full flaps setting and potentially my inability to retract the flaps might lead to my inability to climb sufficiently to do a go around. Additionally, the gear was hanging down below the plane and would have added further drag. I did not believe that I could pull the breaker and pump the gear into place in time, while still maintaining control of the aircraft." The pilot reported that he landed the airplane as "softly and slowly" as possible. The airplane landed on its fully extended nose wheel and partially extended main landing gear. The airplane rolled onto its right wing and horizontal stabilizer and skidded to a stop on the runway. The airplane was taken to a maintenance facility where it was put on jacks in order to check the landing gear system. When the landing gear handle was put in the up position, the landing gear retracted normally. When the gear handle was put in the down position, the landing gear extended, but did not extend to the fully down position. The landing gear hydraulic reservoir was checked for hydraulic fluid. The mechanic who performed the inspection reported that the fluid level was below the pick-up point of the electrically activated hydraulic pump. However, there was enough hydraulic fluid available in the reservoir for the emergency manual gear extension to operate. The mechanic added 6 to 8 ounces of hydraulic fluid. After the hydraulic fluid was added, the landing gear was cycled 4 to 5 times and the landing gear retracted and fully extended normally. The mechanic reported that the emergency gear extension procedures were followed to pump the landing gear down and the landing gear went to the fully extended position. The inspection of the battery revealed that it was weak and required recharging. The airplane was repaired. The maintenance logbook entries indicated that the maintenance facility serviced the aircraft's battery, serviced the hydraulic system with MIL-5606 hydraulic fluid, replaced the engine drive vacuum pump, checked the vacuum system check valves, replaced the vacuum regulator filter, adjusted the regulator for 5 inches of mercury at 2,100 RPM, and replaced the auxiliary radio antenna. The airplane sustained substantial damage when the partially extended main landing gear collapsed during landing. The pilot reported that the attitude indicator failed during cruise flight about 30 minutes after departure. When he was 10 miles from the airport, he slowed the airplane to 110 kts and put in ten degrees of flaps and lowered the landing gear switch. He reported seeing a green light on the gear position indicator. The pilot reported that both the primary and secondary radios failed, the HSI failed, and that the electrically powered primary altimeter was stuck at 2,900 feet. He reported that he used his portable radio to communicate with the tower. The airplane was on short final for landing with full flaps and idle power when the control tower informed the pilot that the wheels were not down. The pilot chose to continue the landing rather that perform a go-around. The pilot reported, "I did not add power for a go around as it appeared that the full flaps setting and potentially my inability to retract the flaps might lead to my inability to climb sufficiently to do a go around. Additionally, the gear was hanging down below the plane and would have added further drag." The airplane landed on its fully extended nose wheel and partially extended main landing gear. The airplane rolled onto its right wing and horizontal stabilizer and skidded to a stop on the runway. The airplane was taken to a maintenance facility where it was put on jacks in order to check the landing gear system. When the landing gear handle was put in the up position, the landing gear retracted normally. When the gear handle was put in the down position, the landing gear extended, but did not extend to the fully down position. The landing gear hydraulic reservoir was checked for hydraulic fluid. The inspection revealed that the fluid level was below pick-up point of the electrically activated hydraulic pump; however, there was enough hydraulic fluid available in the reservoir for the emergency manual gear extension to operate. Six to eight ounces of hydraulic fluid was added to the reservoir. After the hydraulic fluid was added, the landing gear was cycled 4 to 5 times, and the landing gear retracted and fully extended normally. The emergency gear extension procedures were then performed to pump the landing gear down, and the landing gear went to the fully extended position. The inspection of the battery revealed that it was weak and required recharging. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_CHI05LA136.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around, maintenance, autopilot). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- arXiv 2025 · arXiv preprint
ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint
ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
Browse the full corpus — academia portal ↗