# NTSB ATL03LA100: Cessna 172N, N734AG, Orangeburg, SC, May 30, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: May 30, 2003, 14:45 local (18:45 UTC) - Place: Orangeburg, SC - Coordinates: 33.45639, -80.855278 - Nearby events: https://openairdocs.org/map.md?lat=33.4564&lon=-80.8553&mi=10 - Phase of flight: [Emergency descent](https://openairdocs.org/ntsb-phases/600) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 28, 2006 - Report: Approved by Office Director - Parties: Columbia FSDO - NTSB case key (mKey): 57123 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ATL03LA100 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57123/pdf - Page: https://openairdocs.org/ntsb/ATL03LA100 ## Probable cause The pilot's continued operation of the airplane with known deficiencies in the equipment. Also causal was the other maintenance personnel's improper installation of the mixture control linkage bolt that resulted in binding of the mixture control linkage and the post-landing fire. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(total) - mech failure/malf, emergency descent/landing - mixture control,linkage - binding(mechanical) (cause) - miscellaneous,bolt/nut/fastener/clamp/spring - incorrect (cause) - maintenance,installation - improper, other maintenance personnel (cause) - operation with known deficiencies in equipment - continued, pilot in command (cause) - Forced landing, descent - emergency - Fire, landing ## Analysis According to the pilot, during preflight procedures, he noticed that the mixture control was "stuck fully open". The pilot elected to make the flight despite this finding. The pilot stated that it "did not appear to effect the airworthiness" of the airplane. Approximately 20 minutes into the flight the airplane had a partial loss of engine power. The pilot declared an emergency and requested assistance from Columbia Tower. The airplane regained engine power and the pilot elected to return to the departure airport. On final approach, the airplane had a complete loss of engine power, and the pilot conducted an emergency landing in a field. After landing without incident, the pilot observed flames exiting the cowling. Efforts by the pilot to extinguish the fire using the onboard fire extinguisher were unsuccessful, and the airplane was destroyed. Examination of the carburetor showed the mixture control linkage was corroded and not moving freely. Further examination revealed an incorrect bolt had been installed for the mixture control linkage. ## Factual narrative On May 30, 2003, at 1445 eastern daylight time, a Cessna 172N, N734AG, registered to Corsair Enterprise Incorporated and operated by a private pilot, conducted an emergency landing in a field following a loss of engine power near Orangeburg, South Carolina. The personal flight was operated under the provision of Title 14 CFR Part 91, and visual flight rules. Visual meteorological conditions prevailed and a visual flight rules flight plan was filed. The airplane was destroyed by fire, and the pilot reported no injuries. The flight departed Orangeburg Municipal Airport, Orangeburg, South Carolina on May 30, 2003 at 1425. According to the pilot, during pre-flight procedures, he noticed that the mixture control was "stuck fully open" and was not placarded or written up. The pilot elected to make the flight despite this finding. The pilot stated that it "did not appear to affect the airworthiness" of the airplane. Approximately 20 minutes into the flight the airplane had a partial loss of engine power. The pilot declared an emergency and requested assistance from Columbia Tower. The airplane regained engine power and the pilot elected to return to the departure airport. On final approach, the airplane had a complete loss of engine power, and the pilot conducted an emergency landing in a field. After landing without incident, the pilot observed flames exiting the cowling. Efforts by the pilot to extinguish the fire using the onboard fire extinguisher were unsuccessful, and the airplane was destroyed. The pilot stated that prior to the accident flight he taxied the airplane to the fuel pump, and had to shut off the engine by turning the magnetos to the "OFF" position. The pilot also stated that the mixture control lever was stuck in the rich position. Examination of the carburetor showed the mixture control linkage was corroded and not moving freely. Further examination revealed an incorrect bolt had been installed for the mixture control linkage. According to the parts manual for the Cessna 172, bolt number S2323-13-6C-38 is the correct bolt for the mixture control linkage. The bolt found installed on the accident airplane was an AN3 part numbered bolt. Federal Aviation Regulations Part 91.7 (a) states that no person may operate a civil aircraft unless it is in an airworthy condition. According to FAR Part 91.7 (b), the pilot in command is responsible for determining whether the aircraft is in condition for safe flight, and shall discontinue the flight when unairworthy mechanical, electrical, or structural conditions occur. ## Aircraft - Registration: [N734AG](https://openairdocs.org/deregistered/N734AG-2005-08-19), registration cancelled 2005-08-19, S/N 17268698, built 1977 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17268698 - Airframe hours: 2412 - Engines: Lycoming O-320 180 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Business, Part 91 - Registered owner: Corsair Enterprise Inc. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 12, 2002, 129 hours before - Departed: OGB, Orangeburg, SC - Destination: BHM, BIRMINGHAM, AL - Flight plan: VFR - Airport: OGB, Orangeburg Muni, runway 050, 4,500 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 44; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; last flight review March 28, 2003; seat: left; flight hours: 215 total, 128 in this make and model, 142 as pilot in command, 67 in the last 90 days, 8 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 4 knots - Visibility: 9 statute miles - Lowest ceiling: none - Temperature: 79 °F, dew point 55 °F - Altimeter: 29.76 inHg - Observed at: OGB, 3 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20030530013819A](https://openairdocs.org/incident/20030530013819A), May 30, 2003: Cessna 172N, Orangeburg, SC, Substantial damage. (-23) Aircraft experienced loss of engine power while in flight. Partial power was restored and pilot attempted to return to departing airport, Orangeburg… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.