# NTSB CEN12CA597: Bordelon Bruce Kitfox IV, N396BK, Castlerock, MN, July 31, 2012

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: July 31, 2012, 14:10 local (19:10 UTC)
- Place: Castlerock, MN
- Coordinates: 44.545555, -93.136665 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=44.5456&lon=-93.1367&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR go-around: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report July 29, 2013
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: FAA FSDO Minneapolis
- NTSB case key (mKey): 84911
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN12CA597
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/84911/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=84911
- Page: https://openairdocs.org/ntsb/CEN12CA597

## Probable cause

Propeller system failure during a go-around maneuver resulting in a forced landing. Contributing to the severity of damage to the airplane was the postimpact fire.

## Findings

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

- [Propeller system](https://openairdocs.org/ntsb-findings/01046100): Aircraft › Aircraft propeller/rotor · Malfunction (probable cause); cases with it: [Bordelon Bruce KITFOX IV, 1 case](https://openairdocs.org/ntsb-findings/01046100/cases.md?model=05614I4), [All aircraft, 20 cases](https://openairdocs.org/ntsb-findings/01046100/cases.md)

## Sequence of events

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

- [Approach-VFR go-around: Powerplant sys/comp malf/fail](https://openairdocs.org/ntsb-events/340) (defining event); cases with it: [Bordelon Bruce KITFOX IV, 1 case](https://openairdocs.org/ntsb-events/340/sequence.md?model=05614I4), [All aircraft, 820 cases](https://openairdocs.org/ntsb-events/340/sequence.md)

## Analysis

The pilot was flying his experimental airplane, practicing touch-and-go landings on his 1,400 foot long private grass airstrip. The weather was clear. During his third touch-and-go, he determined that he was going to land too long so he made a go-around. As he added power for the go-around, he started to feel vibrations and thought that he had a propeller malfunction. The vibrations continued regardless of power setting, so he shut down the engine and intentionally stalled the airplane about 10 feet above the ground to avoid rolling over when the airplane settled to the ground. The airplane came to rest in a corn field. The pilot saw that a fire had started in the engine compartment after ground impact, so he quickly exited the airplane. A post-crash fire then completely consumed the airplane. Examination of the airplane after the accident did not show any evidence of preimpact mechanical malfunction or abnormalities, although the fire damage was too extensive to specifically determine the reason for presumed propeller malfunction. After the examination, the pilot maintained that he was certain that there was a problem with the propeller and that it was the cause of the accident.

## Factual narrative

The pilot was flying his experimental airplane, practicing touch-and-go landings on his 1,400 foot long private grass airstrip. The weather was clear. During his third touch-and-go, he determined that he was going to land too long so he made a go-around. As he added power for the go-around, he started to feel vibrations and thought that he had a propeller malfunction. The vibrations continued regardless of power setting, so he shut the engine down and intentionally stalled the airplane about 10 feet above the ground to avoid rolling over when the airplane settled to the ground. The airplane came to rest in a corn field. The pilot saw that a fire had started in the engine compartment after ground impact, so he quickly exited the airplane. A post-crash fire then completely consumed the airplane. Examination of the airplane after the accident did not show any evidence of preimpact mechanical malfunction or abnormalities, although the fire damage was too extensive to specifically determine the reason for presumed propeller malfunction. After the examination, the pilot maintained that he was certain that there was a problem with the propeller and that it was the cause of the accident.

## Aircraft

- Registration: [N396BK](https://openairdocs.org/deregistered/N396BK-2018-01-19), registration cancelled 2018-01-19, S/N C94100070, built 2003 (OpenAirDocs)
- Reported make and model: BORDELON BRUCE KITFOX IV (1200)
- Registry model: [Bordelon Bruce KITFOX IV](https://openairdocs.org/model/bordelon-bruce-kitfox-iv) (registry code 05614I4) (OpenAirDocs)
- Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs)
- Category: Airplane, amateur-built
- Serial number: C9400070
- Airframe hours: 35
- Engines: Subaru EA B1 100 horsepower reciprocating
- Damage: Destroyed
- Fire: On-Ground
- Flight: Personal, Part 91
- Operator: Svien Benny H
- Registered owner: Svien Benny H
- Airworthiness certificate: Special, Experimental (Special)
- Last inspection: Condition, May 30, 2012, 5 hours before
- Departed: 000, Castlerock, MN
- Destination: 000, Castlerock, MN
- Airport: 000, Private Landing Strip, runway 36, 1,400 × 80 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 61; injuries: none; private; airplane ratings: single-engine land; last flight review July 15, 2012; seat: front; flight hours: 250 total, 225 in this make and model, 10 in the last 90 days, 5 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 200° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 82 °F, dew point 43 °F
- Altimeter: 30.07 inHg
- Observed at: SYN, 15 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 20120731016169A](https://openairdocs.org/incident/20120731016169A), Jul 31, 2012: Bordelon Bruce KITFOX IV, Castle Rock Twp, MN, Destroyed. Pilot attempted landing at his private field and felt that he was going to land long. He began a go-around and started a right hand turn as to avoid a low…

## Other investigations on N396BK (2)

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.

- [NTSB CEN10CA304](https://openairdocs.org/ntsb/CEN10CA304), Jun 7, 2010: Bordelon Kitfox IV (N396BK), Stanton, MN, substantial damage. Probable cause: The pilot’s inadvertent propeller blade pitch change and subsequent loss of forward thrust.
- [NTSB CEN09CA592](https://openairdocs.org/ntsb/CEN09CA592), Sep 18, 2009: Bordelon Kitfox IV (N396BK), Dodge Center, MN, substantial damage. Probable cause: The pilot's improper glide path during landing.

## Docket (3 files)

The files NTSB released with the investigation on July 15, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=84911. 6.7 MB in all.

- Record of Telephone Conversation with Pilot (item 1, .PDF, 41 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40396341&FileExtension=.PDF&FileName=Record%20of%20Telephone%20Conversation%20with%20Pilot-Master.PDF
- Photo 1 Airplane Wreckage (item 2, .PDF, 3.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40396342&FileExtension=.PDF&FileName=Photo%201%20Airplane%20Wreckage-Master.PDF
- Photo 2 Airplane Wreckage (item 3, .PDF, 3.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40396343&FileExtension=.PDF&FileName=Photo%202%20Airplane%20Wreckage-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.
