6 Aug 2008: Ouzts Rodney Rutan-LongEZ — David Rowe

6 Aug 2008: Ouzts Rodney Rutan-LongEZ (N622EZ) — David Rowe

No fatalities • Winder, GA, United States

Probable cause

The failure of the left brake due to contamination of the brake fluid.

— NTSB Determination

Accident narrative

On August 6, 2008, at 1400 eastern daylight time, an amateur-built Rutan-LongEZ, N622EZ, was substantially damaged while landing at Winder-Barrow Airport (WDR), Winder, Georgia. The certificated private pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the flight that originated at Gwinnett County Airport (LZU), Lawrenceville, Georgia. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91.

According to the pilot, he purchased the airplane about 2 years prior to the accident; however, the accident flight was the first time he had flown it. The previous owner had flown about 7 hours in the airplane prior to the accident pilot purchasing it.

The accident pilot reported no maintenance had been performed to the brake system since he owned the airplane; however, brake fluid was added to both master cylinders about 8 weeks prior to the accident. At that time, the pilot performed taxi testing. He experienced "a little brake fade" which he described as a "softening of the brakes" or less resistance than normal. The "brake fade" was the same for the left and right brakes. The pilot did not think this was a problem but did further examine the brake system. His examination revealed both brake lines were clear and he did not observe any bubbles in the lines; however, he did observe about a 1/2-inch area of brake fluid that had "lost color" and had faded from red to pink. The pilot commented that the airplane did not have wheel pants installed at the time of the taxi testing. Additionally, the brake lines were independent of each other.

On the day of the accident, prior to the test flight, the pilot installed wheel pants on the airplane. He then performed about 2 hours of taxi testing and taxied about 1/8 mile to the runway, which included 5 left turns (steering on the ground was performed through differential braking). The pilot noted no problems with the brakes during taxi or before takeoff.

The takeoff and flight to WDR were uneventful, and the pilot flew a final approach to runway 31, at 80 knots, with the landing brake deployed. Prior to crossing the touchdown zone, he retracted the landing brake, touched down past the numbers and applied both brakes. The left rudder/brake pedal at first functioned normally, then "sank to a stop." The aircraft veered to the right, off the edge of the runway, where it struck a runway sign before coming to rest about midfield.

A Federal Aviation Administration (FAA) inspector examined the airplane after the accident. According to the inspector, when he tested the brakes, the left brake never engaged and the right brake functioned normally. An examination of the brake fluid revealed that the fluid in the line for the left brake was several shades lighter than the fluid in the line for the right brake. No additional mechanical malfunctions were noted with the brake system. The inspector also reported substantial damage to the fuselage and bulkhead.

Examination of the maintenance logbooks for the airplane revealed the airplane was issued a Special Airworthiness Certificate on November 9, 2005, at a tachometer time of 0 hours. The next entry in the airframe logbook was for a condition inspection completed on July 26, 2008, at a tachometer time of 7 hours. According to the logbook entry, during the inspection, the "wheels were serviced," and a retract test was performed on the nose gear. No anomalies were noted in the entry.

Contributing factors

  • cause Landing gear brakes system — Failure
  • cause Fluid condition

Conditions

Weather
VMC, wind 310/10kt, 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.