# NTSB CEN18FA358: Beech B60, N1876L, Fort Walton Beach, FL, August 30, 2018 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: August 30, 2018, 10:30 local (15:30 UTC) - Place: Fort Walton Beach, FL - Coordinates: 30.494722, -86.574447 - Nearby events: https://openairdocs.org/map.md?lat=30.4947&lon=-86.5744&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Fatal - Injuries: 4 fatal - Status: Completed, report April 20, 2020 - Report: Approved by Office Director - NTSB office: Central Region - Parties: Lycoming Engines, FAA FSDO, Textron Aviation - NTSB case key (mKey): 98196 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN18FA358 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98196/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98196 - Page: https://openairdocs.org/ntsb/CEN18FA358 ## Probable cause The pilot's controlled flight into terrain after misidentifying the destination airport during a period of restricted visibility due to weather. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Beech B-60, 2 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=1153605), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md) - [Performance/control parameters: altitude](https://openairdocs.org/ntsb-findings/01062012): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Beech B-60, 3 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md?model=1153605), [All aircraft, 1,310 cases](https://openairdocs.org/ntsb-findings/01062012/cases.md) - [Ceiling/visibility/precip: rain](https://openairdocs.org/ntsb-findings/03035035): Environmental issues › Conditions/weather/phenomena · Effect on personnel (probable cause); cases with it: [Beech B-60, 1 case](https://openairdocs.org/ntsb-findings/03035035/cases.md?model=1153605), [All aircraft, 56 cases](https://openairdocs.org/ntsb-findings/03035035/cases.md) - [Ceiling/visibility/precip: low visibility](https://openairdocs.org/ntsb-findings/03035015): Environmental issues › Conditions/weather/phenomena · Effect on personnel (probable cause); cases with it: [Beech B-60, 2 cases](https://openairdocs.org/ntsb-findings/03035015/cases.md?model=1153605), [All aircraft, 175 cases](https://openairdocs.org/ntsb-findings/03035015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-descent: VFR encounter with IMC](https://openairdocs.org/ntsb-events/401); cases with it: [Beech B-60, 1 case](https://openairdocs.org/ntsb-events/401/sequence.md?model=1153605), [All aircraft, 392 cases](https://openairdocs.org/ntsb-events/401/sequence.md) - [Approach: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Beech B-60, 3 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=1153605), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis The commercial pilot and three passengers departed on a cross-country flight in a twin-engine airplane. As the flight neared the destination airport, the pilot canceled his instrument flight rules (IFR) clearance. The approach controller transferred the flight to the tower controller, and the pilot reported to the tower controller that the airplane was about 2 miles from the airport. However, the approach controller contacted the tower controller to report that the airplane was 200 ft over a nearby joint military airport at the time. GPS data revealed that, when pilot reported that the airplane was 2 miles from the destination airport, the airplane's actual location was about 10 miles from the destination airport and 2 miles from the joint military airport. The airplane impacted a remote wooded area about 8 miles northwest of the destination airport. At the time of the accident, thunderstorm cells were in the area. A review of the weather information revealed that the pilot's view of the airport was likely obscured because the airplane was in an area of light precipitation, restricting the pilot's visibility. A review of airport information noted that the IFR approach course for the destination airport passes over the joint military airport. The Federal Aviation Administration chart supplement for the destination airport noted the airport's proximity to the other airport. However, it is likely that the pilot mistook the other airport for the destination airport due to reduced visibility because of weather. The accident circumstances were consistent with controlled flight into terrain. The ethanol detected in the pilot's blood specimens but not in his urine specimens was consistent with postmortem bacteria production. The carbon monoxide and cyanide detected in the pilot's blood specimens were consistent with inhalation after the postimpact fire. ## Factual narrative The Federal Aviation Administration (FAA) chart supplement for DTS noted, in the remarks section, the following: exercise extreme vigilance due to close proximity to Eglin AFB located 6 nautical miles northwest of the airport. Additionally, the instrument approach course for DTS runway 14 (the intended runway for landing) crossed VPS. VPS is a joint-use facility with Eglin AFB. The FAA chart supplement for VPS noted, in the remarks section, a statement about DTS location. On August 30, 2018, about 1030 central daylight time, a Beechcraft B60 airplane, N1876L, impacted terrain near Fort Walton Beach, Florida, during a planned approach to Destin Executive Airport (DTS), Destin, Florida. The commercial pilot and three passengers were fatally injured, and the airplane was destroyed. The airplane was registered to and operated by Henry Leasing Company LLC as a Title 14 Code of Federal Regulations Part 91 personal flight. Visual meteorological conditions prevailed at the time of the accident, and an instrument flight rules (IFR) flight plan had been filed for the cross-country flight, which departed Toledo Executive Airport (TOL), Millbury, Ohio, about 0747. A review of air traffic control communications revealed that the pilot was in contact with the Eglin Air Force Base (AFB) approach controller, who contacted the DTS tower controller at 1028 to report that the an IFR flight was inbound at 12 miles to the northwest. As the airplane approached the destination airport, the pilot canceled his IFR clearance and proceeded under visual flight rules (VFR). The approach controller contacted the DTS tower controller at 1031 to advise that the airplane was operating under VFR. Also at 1031, the DTS tower controller contacted the pilot and asked for the airplane's position. The pilot responded, "we're about 2 out for [runway] 1-4," which was the last communication received from the pilot. GPS data recovered from a portable onboard unit showed the airplane's track as it approached DTS. The last data point, at 1032, indicated that the airplane was at an altitude of 489 ft and a ground speed of 118 knots. At 1033, the approach controller asked the tower controller if the airplane had Eglin AFB and DTS in sight, and the tower controller responded that the pilot reported that the airplane was 2 miles out. The approach controller then stated that the airplane was 200 ft over Eglin AFB. The tower controller tried to contact the pilot, but the pilot did not respond to these transmissions. The airplane wreckage was located in a remote wooded area about 8 miles northwest of DTS and 2.5 miles northwest of Destin-Fort Walton Beach Airport (VPS), Eglin AFB, Florida. Figure 1: GPS Track The Defense Health Agency, Armed Forces Medical Examiner System, Dover AFB, Delaware, conducted an autopsy on the pilot. His cause of death was multiple injuries. Toxicology testing by the Armed Forces Medical Examiner System identified carbon monoxide, cyanide, and ethanol in the pilot'sblood specimens and losartan in the pilot's blood and urine specimens. Losartan is a prescription medication used to treat high blood pressure; the pilot had previously reported this drug to the FAA. The convective outlook for the day of the accident indicated a slight risk of general airmass-type thunderstorms over the route of flight and the accident site. The weather observations for VPS starting at 0855 and through 1023 indicated that lightning was observed in the distance south of the airport when a thunderstorm was reported in the terminal area. As the thunderstorm passed over VPS between 1023 and 1039, marginal VFR conditions were reported, but the remarks section indicated that visibility was estimated at 2 miles in likely heavy rain showers to the north and northeast, with defined thunderstorm cells noted 2 miles east and 4 miles west of the station moving northward. Restricted visibility conditions were in the general direction of the accident site. No strong gusting wind was noted during the period. The weather observations for DTS also noted lightning in the distance south and southwest from 0731 to the time of the accident. At the time of the accident, a short period of marginal VFR conditions were reported due to ceilings broken at 1,500 ft above ground level. Light precipitation was reported after the time of the accident, and no strong outflow wind or gusts were reported. The airplane impacted trees and the wreckage path was on about a 067° heading and 380 ft long. The airplane's nose cone was located near the initial impact point, and the left-wing-tip fuel tank and right outboard wing were near the beginning of the wreckage path. The right horizontal stabilizer and elevator were fragmented and located along the wreckage path. A tree limb, which was about 4 inches in diameter and had been cut as a result of the airplane's impact, was also in the wreckage path. The airplane came to rest inverted. A postcrash fire consumed most of the cabin and inboard section of the wings. Control continuity was established from the elevator bellcranks to the swaged ends in the cabin and from the rudder control surface to the torque tubes. The position of the landing gear and flaps could not be determined due to impact damage. Both engines had extensive impact and fire damage with the right engine located to the right of the main wreckage and the left engine located in front of the main wreckage. All four magnetos were destroyed by fire and could not be tested. The top set of spark plugs were removed, and the cylinders were examined using a borescope. The right engine fuel servo screen was clear of debris. The right engine turbocharger compressor would not rotate, but the blades exhibited damage consistent with rotation during operation. The left engines turbocharger compressor was unable to be examined because of extensive fire damage. Both three-bladed propellers had separated and were found next to their respective engines. The bladesexhibited twisting and impact damage. Although the examination of the airframe and engines was limited due to fire and impact damage, the parts examined revealed no preimpact abnormalities that would have precluded normal operation. A portable Garmin GPSMAP 496 unit was located in the wreckage. The unit, which had sustained impact damage, was sent to the NTSB's Vehicle Recorder Laboratory for download of its nonvolatile memory. Track log data were recovered for the accident flight. ## Aircraft - Registration: [N1876L](https://openairdocs.org/deregistered/N1876L-2019-02-06), registration cancelled 2019-02-06, S/N P-386, built 1976 (OpenAirDocs) - Reported make and model: Beech B60 - Registry model: [Beech B-60](https://openairdocs.org/model/beech-b-60) (registry code 1153605) (OpenAirDocs) - Registry engine: [Lycoming TI0-541 series](https://openairdocs.org/engine/lycoming-ti0-541-series) (registry code 41536, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: P-386 - Year built: 1976 - Airframe hours: 4167.7 - Engines: Lycoming TIO-541 reciprocating; Lycoming TIO-541 reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Personal, Part 91 - Operator: Henry Leasing Co Llc - Registered owner: Henry Leasing Co Llc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 15, 2018 - Departed: KTOL, Toledo, OH - Destination: KDTS, Destin, FL - Flight plan: IFR - Airport: KDTS, Destin Executive Airport, runway 14, 5,001 × 100 ft, asphalt - Equipment: ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; injuries: fatal; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; seat: left; toxicology performed; flight hours: 2,427 total, 100 in this make and model ## Weather - Conditions: Day - Wind: 60° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 3,000 ft broken - Temperature: 82 °F, dew point 73 °F - Altimeter: 30.11 inHg - Observed at: KVPS ## 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 20180830016109A](https://openairdocs.org/incident/20180830016109A), Aug 30, 2018: Beech B-60, Fort Walton Bea, FL, Destroyed, 4 fatal. Aircraft departed ktol enroute to kdts. Aircraft departed ktol full of fuel. Departure and enroute portion of flight was uneventful. There were thunderstorms… ## Docket (17 files) The files NTSB released with the investigation on March 17, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98196. 14.1 MB in all. - Specilaist's Factual Report- GPS (item 1, .PDF, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481241&FileExtension=.PDF&FileName=Specilaist%27s%20Factual%20Report-%20GPS-Master.PDF - GPS Data- Attachment 1 (item 2, .CSV, 18 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481242&FileExtension=.csv&FileName=GPS%20Data-%20Attachment%201-Master.csv - GPS Track (item 3, .PDF, 527 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481243&FileExtension=.PDF&FileName=GPS%20Track-Master.PDF - Location Overview (item 4, .PDF, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481244&FileExtension=.PDF&FileName=Location%20Overview-Master.PDF - Approach Plate - KDTS (item 5, .PDF, 246 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481245&FileExtension=.PDF&FileName=Approach%20Plate%20-%20KDTS-Master.PDF - Fuel Record (item 6, .PDF, 269 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481246&FileExtension=.PDF&FileName=Fuel%20Record-Master.PDF - Chart Supplement (Facility Directory) (item 7, .PDF, 114 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481247&FileExtension=.PDF&FileName=Chart%20Supplement%20(Facility%20Directory)-Master.PDF - Alnot (item 8, .PDF, 123 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481248&FileExtension=.PDF&FileName=ALNOT-Master.PDF - Air Traffic Control Transcript (item 9, .PDF, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481249&FileExtension=.PDF&FileName=Air%20Traffic%20Control%20Transcript-Master.PDF - ATC Radar Track (item 10, .PDF, 353 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481250&FileExtension=.PDF&FileName=ATC%20Radar%20Track-Master.PDF - ATC Summary (item 11, .PDF, 153 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481251&FileExtension=.PDF&FileName=ATC%20Summary-Master.PDF - Pilot Records (Excerpts) (item 12, .PDF, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481252&FileExtension=.PDF&FileName=Pilot%20Records%20(Excerpts)-Master.PDF - Photos (item 13, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481253&FileExtension=.PDF&FileName=Photos-Master.PDF - Maintenance Records (Excerpts) (item 14, .PDF, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481254&FileExtension=.PDF&FileName=Maintenance%20Records%20(Excerpts)-Master.PDF - Statement of Party Representatives to NTSB Investigation (item 15, .PDF, 158 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481255&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Master.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 16, .PDF, 229 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481256&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Master.PDF - Weather Study (item 17, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40481257&FileExtension=.PDF&FileName=Weather%20Study-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.