Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 21, 2000 · Bollinger BD-4 · N108BC

Hedrick, IA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 21, 2000
Injury Outcomes
1 injury (1 minor injury)
Location
Hedrick, IA
Aircraft
Bollinger BD-4
Tail Number
N108BC
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI01LA022

The experimental airplane sustained substantial damage on contact with a fence and subsequent nose over during a go-around at a private airstrip. The pilot stated, "I aquired permission by telephone from the owner to land at this runway and I also asked him about the condition of the runway. He did not tell me about the trees or the fence." The airstrip owner stated that he would advise pilots that call for landing permission of the current field condition and approach information.

NTSB Probable Cause

the pilot not obtaining/maintaining clearance from the fence. A factors was fence.

Full Narrative

On October 21, 2000, at 1515 central daylight time, a Bollinger BD-4, N108BC, piloted by a private pilot, sustained substantial damage on contact with a fence and subsequent nose over, during a go-around from runway 27 at a private airstrip near Hedrick, Iowa. The personal flight was operating under 14 CFR Part 91. Visual meteorological conditions prevailed at the time of the accident. No flight plan was on file. The pilot reported minor injuries. The flight departed from Fairfield Municipal Airport, Fairfield, Iowa, at 1450. The pilot stated, "I approached the 2500 foot grass runway #27 and discovered that I would have to clear 50' trees that were indented on the runway about 50' thus shortening the usable r/y to about 1800'. At this point I made a go-around to approach again. Upon my 2nd approach I did my landing check list and reviewed short field landing procedure. Final approach was done at a steeper angle and at 65 kts to clear the trees. I had full flaps on this approach but power was completely off as I made my round out to flair. I had determined previously that I should touch down no less than 800 feet before the end of the runway to allow enough distance for rollout. Everything seemed perfect until the flair. At about 1 ft off the ground the flair seemed to be going on too long so at the moment I decided to add throttle [and] go around the aircraft touched the r/y in a full stall and was slowed by the 4" to 6" grass but the engine was now at full power. At this point, it seemed the best thing to do was to try to take off again because I no longer had enough room to stop before hitting the fence at the end of the runway. This decision was based on the fact that my BD-4 is configured as a short takeoff and landing aircraft relative to other BD-4s and because I was at full throttle now with maybe 500 ft left to stop. My hope was to clear the fence with in ground effect if necessary, maybe even jump the fence. The highest wire of the fence was about 4 1/2 feet high and I caught the top wire on the midpoint of my landing gear. The plane slowed down to almost a stop on the other side of the fence and then slowly turned over on to the right wing tip and prop and then continued slowly to an upside down position. The plane ended up about 75 ft beyond the other side of the fence. The question is why did my flair continue too long and I feel the answer is because my vernier throttle control clicked up a detent or so increasing the RPM just as I was on my flair. This had happened to me before but I thought I had fixed it. I can always tell when this happens because I can hear the increase in RPM but this time I didn't hear it because I was wearing ear plugs in addition to my head set because of the very noisey cabin during flight." The pilot also stated, "I aquired permission by telephone from the owner to land at this runway and I also asked him about the condition of the runway. He did not tell me about the trees or the fence." The pilot's safety recommendation was that "more information about the runway conditions and approach would have made the difference." In a telephone interview, the airstrip owner confirmed that the pilot called to get permission. He stated that the runway direction is about 270 degrees true. He said that its length is about 2,500 feet and there is a tree on the runway's north edge near its northeast corner. He confirmed the pilot's approximation of 1,800 feet of useful runway length. The airstrip owner stated that he would advise pilots that call for landing permission of the current field condition and approach information.

Flight

Event TypeAccident
Event Time15:15 CDT
Nearest Airport0nm
Runway27
Runway Length2500 ft
Runway Width50 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBollinger BD-4
Tail NumberN108BC
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsFord · 3.8 L V-6 · Reciprocating · 190
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 50 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind170° @ 9 kt, gusting 17 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point16 C / 12 C
Altimeter30.00 inHg
Observation Time19:53
Weather SourceWFAC

Appendix: Source Data