Skip to content

CHI04LA038

2003-11-24 · Poplar Bluff, Missouri, United States · None · 1 aircraft · Status: Completed

Airport POF

Current FAA registration · N200GC

Make / Model
CESSNA 340A
Year of manufacture
1978 · 25 years old at event
Engine
CONT MOTOR TSIO-520 SER (300 hp)
Seats / Engines
6 seats · 2 engines
Last airworthiness date
19780525
ADS-B equipped
Yes — Mode-S A1929C

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

Failure to maintain directional control during landing. Collapse of the nose landing gear, the muddy grass/turf and the berm were contributing factors.

Factual narrative

On November 24, 2003, at 0800 central standard time, a Cessna 340A, N200GC, piloted by an airline transport pilot, was substantially damaged when it departed runway 36 (5,007 feet by 100 feet, asphalt) during landing at the Poplar Bluff Municipal Airport (POF), Poplar Bluff, Missouri. The nose landing gear subsequently collapsed when the aircraft encountered soft, muddy turf adjacent to the runway and impacted a berm. Visual meteorological conditions prevailed. The pilot reported no injuries. The flight was being conducted under 14 CFR Part 91 and was not on a flight plan at the time of the accident. The flight departed the Jefferson City Memorial Airport on an instrument flight rules (IFR) flight plan with an intended destination of POF. The pilot reported that he canceled his IFR flight plan prior to entering the traffic pattern at POF, completing the remainder of the flight under visual flight rules. In the pilot's written statement, he reported that everything was normal throughout the flight until short final, just prior to touchdown. He stated that winds were from 320 degrees at 6 knots. The pilot noted that the aircraft was crabbed into the wind in order to compensate for the slight left crosswind. When he thought that the landing was assured, he selected full flaps and attempted to align the nose of the aircraft with the runway for touchdown. He stated: "I felt no right rudder control. I observed that the right rudder pedal was fully deflected to the right. I tried to get it loose or back to the normal position with my foot to no avail." The pilot reported that after touchdown the aircraft "veered" to the left. Attempts to correct to the right were unsuccessful, according to the pilot. He noted, "I tried using differential power to maintain runway alignment but was unable. At this point, I reduced power back to the stops/idle, trying to maneuver the aircraft the best I could. During this time I had no right rudder control. Once the aircraft [came] to a complete stop, it was shut down. Before leaving the aircraft, I looked at both rudder control pedals and they both appeared to be in the normal position." Post-accident inspections by a local mechanic and a Federal Aviation Administration Maintenance Inspector confirmed rudder control continuity and brake system integrity. Full rudder travel, without restriction or binding, was observed. Rudder pedal inputs produced the corresponding rudder movement. Although the nose landing gear had collapsed, no anomalies with the nose wheel steering system which could be attributed to a pre-impact malfunction were observed. The brake system appeared to be intact and to operate normally. The twin-engine airplane was substantially damaged when it departed runway 36 during landing. The nose landing gear collapsed when the aircraft encountered soft, muddy turf adjacent to the runway and subsequently impacted a berm. The pilot reported that everything was normal throughout the flight until short final, just prior to touchdown. He stated that winds were from 320 degrees at 6 knots. The pilot reported that when he attempted to align the nose of the aircraft with the runway for touchdown, he had no right rudder control. He stated: "I observed that the right rudder pedal was fully deflected to the right. I tried to get it loose or back to the normal position with my foot to no avail." After touchdown the aircraft "veered" to the left. Attempts to correct to the right were unsuccessful. The pilot noted, "I tried using differential power to maintain runway alignment but was unable. At this point, I reduced power back to the stops/idle, trying to maneuver the aircraft the best I could. During this time I had no right rudder control. Once the aircraft [came] to a complete stop, it was shut down." Post-accident inspection confirmed rudder control continuity and brake system integrity. Full rudder travel, without restriction or binding, was observed. Rudder pedal inputs produced a proper, corresponding rudder movement. No anomalies with the nose wheel steering system which could be attributed to a pre-impact malfunction, were observed. The brake system appeared to be intact and to operate normally. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_2003_CHI04LA038.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type or causal vocabulary (maintenance). All research papers