# NTSB CHI97LA154: Cessna 340A, N171DB, Fort Wayne, IN, June 3, 1997

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: June 2, 1997, 23:25 local (Jun 3, 1997, 04:25 UTC)
- Place: Fort Wayne, IN
- Coordinates: 41.070858, -85.169609 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=41.0709&lon=-85.1696&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report February 2, 1998
- Report: Approved by Office Director
- NTSB case key (mKey): 10584
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI97LA154
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/10584/pdf
- Page: https://openairdocs.org/ntsb/CHI97LA154

## Probable cause

the pilot did not comply with the decision height and his attention was diverted from his cockpit scan.  The factors involved were the weather conditions were at landing minimums and a flight to his destination alternate was not performed.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Undershoot, approach
  - weather condition - low ceiling
  - decision height - not complied with, pilot in command (cause)
  - diverted attention, pilot in command (cause)
  - weather condition - below approach/landing minimums (contributing factor)
  - flight to destination alternate - not performed, pilot in command (contributing factor)
  - light condition - dark night
- In flight collision with terrain/water, approach - faf/outer marker to threshold (ifr)

## Analysis

While flying his ILS approach with 1 mile visibility and a 200 foot ceiling, the pilot was able to see the runway lights to the right side of the airplane upon reaching decision height, but chose a missed approach.  The second approach resulted in the same conditions.  On the third approach, the pilot requested a radar surveillance approach coupled with the ILS approach for glide slope information. The pilot stated 'I fixed my eyes on the runway and inadvertently descended below the glide path and landed short of the runway.'  No discrepancies were discovered with the Nav #1 or Nav #2 instrumentation regarding the ILS centering, deflection and sensitivity.

## Factual narrative

On June 02, 1997, at 2325 eastern standard time (est), a Cessna 340A, N171DB, registered to Exterior Designing, Inc., of Hoagland, Indiana, piloted by an instrument rated private pilot, was substantially damaged when it collided with the terrain approximately one mile from the runway 05 threshold, at the Fort Wayne Municipal Airport, Fort Wayne, Indiana.  The pilot flew two unsuccessful ILS approaches to runway 05.  The pilot then requested the third approach to be a surveillance approach to runway 05.  The pilot reported no injuries.  The personal 14 CFR Part 91 flight was operating on an IFR flight plan.  Instrument meteorological conditions prevailed at the time of the accident.  The flight departed El Reno, Oklahoma, at 1900 cdt, with the intended destination of Fort Wayne, Indiana.

While en route to Fort Wayne, the pilot received a weather update that was reported as IFR conditions with one mile visibility and a 200 foot ceiling.  The pilot decided to continue on to Fort Wayne.  The pilot flew the ILS approach and "upon reaching the one mile marker the indicator swung to the right indicating we were off course, one quarter mile left of the center line."  The pilot was able to see the runway lights to the right side at decision height but chose to make a missed approach.  The pilot flew a second ILS approach with the same results.  On the third approach, the pilot requested a radar surveillance approach (heading information) coupled with the ILS for glide slope information.  On the third approach the pilot stated "I fixed my eyes on the runway and inadvertently descended below the glide path and landed short of the runway."  The pilot went on to say "Pilot must not become focused on one item, he must continue scanning all instruments and always keep in mind his decision height when flying any approaches."  The pilot also said, "Airplane had no mechanical problems."

Examination of both Nav #1 and Nav #2 revealed that both ILS circuits operated correctly for ILS centering, deflection, and sensitivity.

## Aircraft

- Registration: N171DB (not matched to a registry record)
- Reported make and model: Cessna 340A
- Category: Airplane
- Serial number: 340A-1257
- Airframe hours: 2230
- Engines: Continental TSIO-520 325 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Exterior Designing, Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 21, 1996, 40 hours before
- Departed: F28, EL RENO, OK
- Destination: FWA, IN
- Flight plan: IFR
- Airport: FWA, Fort Wayne International, runway 5, 12,000 × 150 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 62; private; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 5,988 total, 935 in this make and model, 5,988 as pilot in command, 54 in the last 90 days, 26 in the last 30 days, 7 in the last 24 hours

## Weather

- Conditions: Instrument (IMC), Night/dark
- Wind: 50° at 14 knots
- Visibility: 1.5 statute miles
- Lowest ceiling: 100 ft overcast
- Temperature: 57 °F, dew point 57 °F
- Altimeter: 29.00 inHg
- Observed at: FWA

## 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 19970603012309A](https://openairdocs.org/incident/19970603012309A), Jun 3, 1997: Cessna 340A, Fort Wayne, IN, Substantial damage. .Issed 2 ILS approach. On third a par ILS approach. Saw runway forgot altitude. Busted dh and impacted short of rwy

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.
