# NTSB ERA18LA215: Cessna R182, N1693R, Florence, SC, August 9, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: August 9, 2018, 13:12 local (17:12 UTC) - Place: Florence, SC - Coordinates: 34.186111, -79.723609 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.1861&lon=-79.7236&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report September 27, 2019 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 98053 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA18LA215 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98053/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98053 - Page: https://openairdocs.org/ntsb/ERA18LA215 ## Probable cause The pilot's failure to comply with emergency procedures in the pilot's operating handbook, resulting in the collapse of the main landing gear during landing. Contributing to the accident was the pilot's failure to address the low battery voltage before departure. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Electrical power system](https://openairdocs.org/ntsb-findings/01022400): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [Cessna R182, 2 cases](https://openairdocs.org/ntsb-findings/01022400/cases.md?model=2072734), [All aircraft, 48 cases](https://openairdocs.org/ntsb-findings/01022400/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna R182, 5 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2072734), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined; cases with it: [Cessna R182, 5 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2072734), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) - [Electrical power system](https://openairdocs.org/ntsb-findings/01022400): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [Cessna R182, 2 cases](https://openairdocs.org/ntsb-findings/01022400/cases.md?model=2072734), [All aircraft, 48 cases](https://openairdocs.org/ntsb-findings/01022400/cases.md) - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna R182, 7 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=2072734), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Landing gear system](https://openairdocs.org/ntsb-findings/01023200): Aircraft › Aircraft systems · Incorrect use/operation (probable cause); cases with it: [Cessna R182, 2 cases](https://openairdocs.org/ntsb-findings/01023200/cases.md?model=2072734), [All aircraft, 113 cases](https://openairdocs.org/ntsb-findings/01023200/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Standing-engine(s) start-up: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332); cases with it: [Cessna R182, 2 cases](https://openairdocs.org/ntsb-events/332/sequence.md?model=2072734), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Enroute-cruise: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332) (defining event); cases with it: [Cessna R182, 2 cases](https://openairdocs.org/ntsb-events/332/sequence.md?model=2072734), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Approach-VFR pattern downwind: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Cessna R182, 5 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2072734), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Landing-flare/touchdown: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Cessna R182, 8 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=2072734), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) - [Landing-landing roll: Dragged wing/rotor/float/other](https://openairdocs.org/ntsb-events/093); cases with it: [Cessna R182, 2 cases](https://openairdocs.org/ntsb-events/093/sequence.md?model=2072734), [All aircraft, 319 cases](https://openairdocs.org/ntsb-events/093/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna R182, 8 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072734), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis Before departure on the personal flight, the private pilot reported that the engine had to be started using an auxiliary power supply because the battery was dead; however, he did not determine the reason for the dead battery. After the engine was started, he reported normal electrical system indications. About 10 minutes into the 20-minute flight, the pilot noticed that the electric fuel gauges were reading zero and the ammeter was showing a discharge. He did not consult or comply with emergency procedures from the pilot's operating handbook (POH) for a discharging ammeter and continued to his destination, where he attempted to extend the landing gear using the normal system; however, there was no down-and-locked indication. He confirmed visually that the nose landing gear was down and locked; he performed a fly-by of the air traffic control tower, was informed that the landing gear appeared to be down, and returned for landing. After touchdown, both main landing gear collapsed, the airplane began to veer to the left, and the left wing and horizontal stabilizer contacted the runway. The airplane came to rest in the grass off the left side of the runway. Postaccident examination and operational testing of the normal and emergency landing gear extension and indicating systems revealed no evidence of preimpact failure or malfunction that would have precluded normal operation. Had the pilot shed unnecessary electrical load per the POH when he first noticed the discharging state or pumped the landing gear down using the emergency gear extension mechanism, it is likely that the landing gear would have extended and locked into position. The reason for the electrical system failure was not investigated. ## Factual narrative On August 9, 2018, about 1312 eastern daylight time, a Cessna R182, N1693R, was substantially damaged when its main landing gear collapsed during the landing roll at the Florence Regional Airport (FLO), Florence, South Carolina. The private pilot was not injured. The airplane was owned and operated by a flying club, under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight that originated about 20 minutes earlier from a private airstrip near Andrews, South Carolina.The pilot stated that before departure, he performed a preflight inspection of the airplane using a copy of the checklist from the airplane's Pilot's Operating Handbook (POH). After the completion of the inspection he attempted to start the engine but could not because the battery was dead. A portable electrical power supply was required to start the engine. After the engine was started, he checked all gauges and reported normal indications, including the alternator, which was working. The ammeter indicated zero or a "hair to the right of zero" after the engine was started. Prior to departure he did not have a mechanic troubleshoot the reason for the dead battery. The pilot further stated that after takeoff, he proceeded towards FLO, and about 10 minutes into the flight while flying at 2,500 feet mean sea level, and in communication with Florence Approach Control, he noted the fuel gauges were indicating zero and the ammeter was showing a discharge, or 3/16 to the left of zero. He did not consult, nor did he perform any emergency procedures from the POH pertaining to electrical system fault. He continued to FLO, lowered the landing gear by selecting the landing gear lever to the "GEAR DOWN" position and was cleared to land. Though he visually observed that the nose landing gear was extended, there was no indication from the single light on the instrument panel that all landing gears were down and locked. The pilot raised the landing gear selector handle then lowered it again, but again there was no landing gear down indication from the single light. He performed a flyby of the FLO air traffic control tower and was advised that the landing gear appeared to be down. He entered the downwind leg of the airport traffic pattern for runway 27 which he extended due to an inbound airplane, and at that time the tower controller asked him his intentions, but he was unable to reply because the airplane had lost all electrical power. He turned onto the base and final legs of the airport traffic pattern for runway 27, and performed a shallow approach, touching down first on the main landing gear. During the landing roll about 500 to 1,000 feet down the runway, the main landing gear collapsed, the airplane began to veer to the left, and the left wing and horizontal stabilizer contacted the runway. The airplane came to rest in the grass off the left side of the runway near the intersection ofrunway 09/27 and 01/19. According to personnel involved in recovery of the airplane, inspection of the cockpit prior to recovery revealed the landing gear selector was in the down position and the emergency extension handle was not extended. The airplane was raised from the runway and the right main landing gear was extended and locked by hand, while the left main landing gear was hand pumped into the down and locked position. Prior to lowering, the airplane's battery was turned on and there was insufficient voltage to power the airplane's electrical system. The airplane was then towed to the ramp. Examination of the airplane was performed following recovery by a Federal Aviation Administration inspector. The examination revealed the battery voltage was 11V. The battery was then charged. The airplane was placed on jacks and jacked up, and with the battery connected it was indicating 24.11V. The master switch was turned on, and the gear green down and lock light was illuminated. The landing gear system was first exercised by electrically cycling the gear up, down, then up again. The aural horn was heard during the transition and functioned normally, and the amber gear up and lock light was illuminated when the gear was in the up position. Using the emergency procedures checklist found in the POH, under the emergency procedures section 3, paragraph 3.8, the master switch was turned off to simulate an electrical failure. The gear handle was put into the down position, the landing gear then fell with the force of gravity and were hand pumped into the down and locked position using the emergency hand pump. The master switch was then turned back on and the gear down and lock light was verified as being illuminated. The airplane was then removed from the jacks. No determination was made as to the reason for the electrical failure. According to the Pilot's Operating Handbook, the procedures to perform when the ammeter shows discharge include: 1. Alternator -- OFF 2. Nonessential Radio/Electrical Equipment – OFF 3. Flight –TERMINATE as soon as practical ## Aircraft - Registration: [N1693R](https://openairdocs.org/aircraft/N1693R), registered now, S/N R18200518, built 1978 (OpenAirDocs) - Reported make and model: Cessna R182 - Registry model: [Cessna R182](https://openairdocs.org/model/cessna-r182) (registry code 2072734) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: R18200518 - Year built: 1978 - Airframe hours: 3997.6 - Engines: Lycoming O-540-J3C5D 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 10, 2018 - Departed: PHH, Andrews, SC - Destination: FLO, Florence, SC - Airport: KFLO, Florence Regional, runway 27, 6,502 × 150 ft, asphalt - Equipment: Auto-pilot ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; injuries: none; private; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review June 21, 2018; seat: left; restraint: 3-point; flight hours: 376 total, 90 in this make and model, 256 as pilot in command, 12 in the last 90 days, 3 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 290° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 88 °F, dew point 72 °F - Altimeter: 30.01 inHg - Observed at: KFLO ## 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 20180809010559A](https://openairdocs.org/incident/20180809010559A), Aug 9, 2018: Cessna R182, Florence, SC, Substantial damage. On Thursday August 09, 2018, at approximately 1:12 pm local time, a Cessna R182, with registration number N1693R veered off the side of the runway at Florence… ## Docket (6 files) The files NTSB released with the investigation on February 28, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98053. 1.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 908 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470668&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of NTSB Conversation (item 2, .PDF, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470669&FileExtension=.PDF&FileName=Record%20of%20NTSB%20Conversation-Master.PDF - Statement from Recovery Personnel (item 3, .PDF, 281 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470670&FileExtension=.PDF&FileName=Statement%20from%20Recovery%20Personnel-Master.PDF - FAA Inspector Statement (item 4, .PDF, 63 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470671&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 5, .PDF, 256 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40470672&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Master.PDF - Excerpt from Pilot's Operating Handbook (item 6, .PDF, 30 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40473800&FileExtension=.PDF&FileName=Excerpt%20from%20Pilot%27s%20Operating%20Handbook-Master.PDF 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.