3 Jul 2008: Chomo EAA Biplane B1 — Kimberly L. Bayer

3 Jul 2008: Chomo EAA Biplane B1 (N6WC) — Kimberly L. Bayer

No fatalities • Schuyler, NE, United States

Probable cause

The pilot's failure to maintain clearance from the wire due to his diverted attention resulting in in-flight collision with the wire. Contributing to the accident was the pilot's failure to locate an emergency landing site.

— NTSB Determination

Accident narrative

On July 3, 2008, approximately 1855 central daylight time, a Chomo EAA Biplane B1, N6WC, was substantially damaged when it flew into a cable and subsequently impacted the river below, near Schuyler, Nebraska. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under the provisions of Title 14 Code of Federal Regulations Part 91 without a flight plan. The private pilot sustained serious injuries. The local flight departed Columbus Municipal Airport (OLU), Columbus, Nebraska, at 1817.

According to the accident report filed by the pilot, the airplane rolled into a steep right turn at 500 to 600 feet above ground level and he opened the throttle "too quickly and the engine began to miss"; pulling out carburetor heat did not resolve the situation. As a result, the pilot pulled out the mixture control to clear a "suspected fouled plug", but did so too fast, and too far causing the engine to "almost quit." The engine regained partial power with a change in the mixture setting. An additional mixture control change "cleared [the] plug". The pilot stated that while trouble shooting the loss of engine power the airplane descended to an "altitude only 20 to 25 feet above the river and the airspeed deteriorated to between 70 and 80 MPH." After successfully restoring engine power, the pilot maintained his altitude, applied "full power and let the airspeed build to between 90 and 100 MPH." The pilot did not report changing course or seeking an adequate emergency landing site. Prior to establishing a climb attitude the airplane struck a cable spanning the river.

Statements from witnesses to the accident place the pilot within 2,000 feet of an open air assembly of persons at an altitude of 25 feet just prior to the impact with the cable. Additional witnesses indicated that approximately twenty-five minutes prior to the accident, the pilot "dive bombed" their boats on the Platte River at an altitude of 40 feet causing them to take action to "get the hell out of the way" of the airplanes path.

According to the Federal Aviation Administration (FAA) Inspector, the airplane impacted cables over the North Platte River and subsequently impacted the river. The right wing separated and the fuselage was bent. The pilot was transported to a hospital with broken ribs, among other injuries. An examination of the airframe by the FAA revealed no anomalies.

According to Federal Air Regulation 91.119, Minimum Safe Altitudes, except when necessary for take off or landing, no person may operate an aircraft below "an altitude allowing, if a power unit fails, an emergency landing without undue hazard to persons or property on the surface." In addition, an aircraft may not be operated over a congested area, "or over any open air assembly of persons below 1,000 feet above the highest obstacle within a horizontal radius of 2,000 feet", nor over other than a congested area at an altitude below "500 feet above the surface, except over open water or sparsely populated areas. In those cases, the aircraft may not be operated closer than 500 feet to any person, vessel, vehicle, or structure."

A weather report taken at 1855, for Columbus, Nebraska ,13 nautical miles west of the accident location, shows temperature 80.6 Fahrenheit (F) , dew point 59.0 F, barometric pressure 29.97, visibility 10 miles, wind south 10.4 MPH at the time of the accident. Carburetor icing charts indicate "serious icing at glide power."

Contributing factors

  • Wire
  • cause Altitude — Not attained/maintained
  • cause Pilot
  • Water

Conditions

Weather
VMC, wind 050/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.