# NTSB ERA15CA302: Cessna 206G, N206DZ, Titusville, FL, August 9, 2015

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Data collection · Final report
- Date: August 9, 2015, 10:55 local (14:55 UTC)
- Place: Titusville, FL
- Coordinates: 28.622499, -80.835281 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=28.6225&lon=-80.8353&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300)
- Highest injury: Minor injuries
- Injuries: 1 minor
- Status: Completed, report December 3, 2015
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA
- NTSB case key (mKey): 91735
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA15CA302
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/91735/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=91735
- Page: https://openairdocs.org/ntsb/ERA15CA302

## Probable cause

The pilot's landing with a tailwind at an excessive speed, which resulted in a runway excursion, and collision with a ditch.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 206, 1 case](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=2073302), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md)
- [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 206, 2 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=2073302), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md)
- [Wind: tailwind](https://openairdocs.org/ntsb-findings/03034015): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Cessna 206, 1 case](https://openairdocs.org/ntsb-findings/03034015/cases.md?model=2073302), [All aircraft, 594 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Cessna 206, 2 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2073302), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 206, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=2073302), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 206, 2 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2073302), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The pilot stated that he was conducting a skydiver "jump run", and prior to letting the skydivers out the radio squelch interrupter failed causing a constant static noise. After letting the skydivers out over the airport the pilot set up the descent based on the winds acquired for the previous landing on runway 22. As he circled for landing the manifold pressure indication "dropped off" to zero. The pilot was unsure if he had a partial power loss or a gauge failure. He could not hear or feel the engine indications because of the static noise on the radio squelch and descent profile, so he committed to a power off glide path for his approach. The pilot stated that the airplanes approach speed was about 100 knots prior to the threshold for landing. The airplane touched down beyond the threshold and as the pilot applied full braking the airplane "ballooned" back into the air. The pilot attempted to stop the airplane but was unsuccessful and exited the runway, coming to rest after colliding with a ditch. An examination of the airplane revealed that the empennage and firewall was buckled during the landing sequence. The airplane was equipped with a JPI engine monitor and review of the data did not reveal a loss in engine power during the flight. The wind reported from a nearby weather station revealed that winds were 010 degrees at 6 knots at the time of the accident.

## Factual narrative

The pilot stated that he was conducting a skydiver "jump run", and prior to letting the skydivers out the radio squelch interrupter failed causing a constant static noise. After letting the skydivers out over the airport the pilot set up the descent based on the winds acquired for the previous landing on runway 22. As he circled for landing the manifold pressure indication "dropped off" to zero. The pilot was unsure if he had a partial power loss or a gauge failure. He could not hear or feel the engine indications because of the static noise on the radio squelch and descent profile, so he committed to a power off glide path for his approach. The pilot stated that the airplanes approach speed was about 100 knots prior to the threshold for landing. The airplane touched down beyond the threshold and as the pilot applied full braking the airplane "ballooned" back into the air. The pilot attempted to stop the airplane but was unsuccessful and exited the runway, coming to rest after colliding with a ditch.An examination of the airplane revealed that the empennage and firewall was buckled during the landing sequence. The airplane was equipped with a JPI engine monitor and review of the data did not reveal a loss in engine power during the flight. The wind reported from a nearby weather station revealed that winds were 010 degrees at 6 knots at the time of the accident.

## Aircraft

- Registration: [N206DZ](https://openairdocs.org/aircraft/N206DZ), registered now, S/N 206-0185 (OpenAirDocs)
- Reported make and model: CESSNA 206G
- Registry model: [Cessna 206](https://openairdocs.org/model/cessna-206) (registry code 2073302) (OpenAirDocs)
- Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 206-0185
- Year built: 1964
- Airframe hours: 14971
- Engines: Continental IO-550-F 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Skydiving, Part 91
- Operator: Skydive Space Center
- Registered owner: Nardi Greg
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, August 5, 2015, 5 hours before
- Departed: X21, Titusville, FL
- Destination: X21, Titusville, FL
- Airport: X21, Arthur Dunn Airpark, runway 22, 1,805 × 100 ft, grass/turf
- Equipment: Handheld GPS

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 37; injuries: minor; private, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: helicopter, airplane; medical: class 2, without waivers/limitations; last flight review May 16, 2015; seat: left; restraint: lap only; flight hours: 1,211 total, 89 in this make and model, 1,014 as pilot in command, 89 in the last 90 days, 53 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 10° at 6 knots
- Visibility: 10 statute miles
- Temperature: 86 °F, dew point 75 °F
- Altimeter: 29.95 inHg
- Observed at: TTS, 7 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 20150809013099A](https://openairdocs.org/incident/20150809013099A), Aug 9, 2015: Cessna 206, Titusville, FL, Substantial damage. The accident aircraft, a 1964 Cessna 206, N206DZ, touched down on runway 22, a sod field 1,805? In length, with a tailwind. The aircraft had one occupant on…

## Docket (8 files)

The files NTSB released with the investigation on November 19, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=91735. 9.3 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434080&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Operator Aircraft Accident Report, NTSB Form 6120.1 (item 2, .PDF, 363 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434081&FileExtension=.PDF&FileName=Operator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- FAA Inspector's Statement (item 3, .PDF, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434082&FileExtension=.PDF&FileName=FAA%20Inspector%27s%20Statement-Master.PDF
- Airport Incident Report (item 4, .PDF, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434083&FileExtension=.PDF&FileName=Airport%20Incident%20Report-Master.PDF
- Maintenance Records (item 5, .PDF, 48 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434084&FileExtension=.PDF&FileName=Maintenance%20Records-Master.PDF
- Aircraft Performance (item 6, .PDF, 116 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434085&FileExtension=.PDF&FileName=Aircraft%20Performance-Master.PDF
- JPI Engine Data (item 7, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434086&FileExtension=.PDF&FileName=JPI%20Engine%20Data-Master.PDF
- Accident Photos (item 8, .PDF, 993 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40434087&FileExtension=.PDF&FileName=Accident%20Photos-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.