29 Apr 2010: Rogers Rutan Defiant 40

29 Apr 2010: Rogers Rutan Defiant 40 (N23TR) — Unknown operator

No fatalities • Phoenix, AZ, United States

Probable cause

The failure of the pilot to ensure that the landing gear extension handle was firmly placed in the down position prior to landing.

— NTSB Determination

Accident narrative

On April 28, 2010, about 1740 mountain standard time, a Rogers Rutan Defiant 40 multi-engine airplane, N23TR, sustained substantial damage following a nose landing gear collapse during landing roll at the Phoenix Deer Valley Airport (DVT), Phoenix, Arizona. The certificated airline transport pilot, the sole occupant of the airplane, was not injured. Visual meteorological conditions prevailed for the personal cross-country flight, which was being operated in accordance with 14 Code of Federal Regulations (CFR) Part 91, and a flight plan was not filed. The flight departed the Ontario International Airport (ONT), Ontario, California, about 1605, with DVT as its destination.

In a report submitted to the Safety Board investigator-in-charge (IIC), the pilot reported that after turning on to base leg he lowered the nose gear and initiated a “landing check.” The pilot stated that the airplane touched down about 1,000 feet down the runway at the “normal rate of descent” and with a slight left crab. The pilot reported, “following initial touchdown and immediately upon placing weight on the nose gear, the nose of the aircraft settled to the ground and the nose gear handle quickly popped out [of] the down position. The aircraft came to a stop left of centerline.”

A Federal Aviation Administration (FAA) inspector assigned to the Scottsdale Flight Standards District Office (FSDO), Scottsdale, Arizona , examined the airplane and reported that its forward-mounted rudder had sustained substantial damage.

On May 6, 2010, a FAA airworthiness inspector assigned to the Fresno FSDO, Fresno, California, conducted an examination of the accident airplane’s nose landing gear’s extension/retraction system. The inspector reported that it was his assessment during an evaluation of the nose landing gear operation that the gear may not have been “positively” down and locked, as witnessed by the alignment marks or witness marks for the nose landing gear. The inspector further reported that during the examination the system was operated several times, and that each time if the gear handle was not placed “down firmly and hard” the alignment marks were not indicating a “SAFE” condition. The inspector stated, “When placing the gear handle down but not hard it ‘appears’ that the nose gear could be safe and down and locked, but it’s not. Taxiing on the ground that causes any sudden bounce or bump could assist the nose gear to collapse, since it’s not positively down and locked.”

The pilot further reported that the down and lock indication consisted of a mechanical alignment of arrows placed down by the right ankle of the pilot. At the conclusion of the gear swings, it was found that the nose gear could be placed in "transition" vice down and locked. He also reported that the indicator arrow misalignment is extremely difficult to perceive. The pilot has since redesigned the nose gear down and locked indicator to be more easily viewed.

At 1753, about 13 minutes after the accident, the automated surface observing system located at DVT reported wind 240 degrees at 18 knots with gusts to 29 knots. Peak wind of 240 degrees at 29 knots was reported at 48 minutes passed the hour, or about 8 minutes after the accident.

Contributing factors

  • cause Pilot
  • factor Design

Conditions

Weather
VMC, wind 240/18kt, 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.