30 Jun 2015: SHORT BROS SD3 60 VARIANT100 — TRANS EXECUTIVE AIRLINES OF HAWAII

30 Jun 2015: SHORT BROS SD3 60 VARIANT100 (N221LM) — TRANS EXECUTIVE AIRLINES OF HAWAII

No fatalities • Kapolei, HI, United States

Probable cause

The pilots’ failure to extend the landing gear before landing. Contributing to the accident was the pilots’ failure to complete the Before Landing checklist.

— NTSB Determination

Accident narrative

On June 29, 2015, about 1944 Hawaiian standard time, a Short Bros SD3-60, N221LM, sustained substantial damage following a gear up landing at the Kalaeloa Airport [John Rogers Field] (JRK) Kapolei, Hawaii. The airplane was registered to and operated by Trans Executive Airlines of Hawaii Inc., under the provisions of Title 14 Code of Federal Regulations Part 91. The airline transport pilot and commercial pilot, the only occupants of the airplane, were not injured. Visual meteorological conditions prevailed and instrument flight rules (IFR) flight plan was filed for the flight check flight which originated from Honolulu International Airport, Honolulu, Hawaii at about 1850.

The flight was a scheduled flight check for the first officer. The crew reported that prior to landing, they thought they had completed the Before Landing checklist. One of the checklist items was to extend the landing gear and ensure it was down. During the landing roll, about a few hundred feet after touchdown, and as the airplane's nose was lowered, the forward bottom section of the fuselage, made contact with the runway surface. The airplane had a tricycle landing gear that used a fully retractable nose gear and a partially retractable main gear. Once the airplane came to a stop, the crew safely egressed.

Examination of the airplane wreckage by a Federal Aviation Administration Inspector revealed that the underside of the fuselage, near the nose wheel, sustained damage. Further assessment of the damage by the National Transportation Safety Board (NTSB), determined that there was structural damage. An operation check of the airplane's landing gear revealed no anomalies.

The captain completed his flight review on November 11, 2014 and had logged 20,230 hours of total flight time. 6,011 hours were logged in the accident make and model of airplane. The first officer completed his flight review on May 16, 2015 and had reported that he had 272 hours of total flight time. 29 hours were logged in the accident make and model of airplane.

During interviews with the NTSB, investigator-in-charge, the flight crew reported that they flew several approaches and landings at JRK. When the accident occurred, it was during their last approach and landing, which upon completion, they had intended on departing JRK. During this approach and landing, the flight crew stated that they landed with the landing gear inadvertently retracted.

According to the flight crew, the warning horn to advise them that the landing gear was not extended, did not activate on final, since they were flying a partial flap approach. According to the airplane's technical information, during a partial flap approach, the airplane's warning horn is designed to activate only when either power lever is pulled back to the flight idle position. The power required to maintain airspeed on the partial flap approach can be more than flight idle position and therefore the landing gear warning horn would not activate.

The flight crew reported no major distractions during the approach and said that they were not rushed. During their last traffic pattern at JRK, the captain communicated with the Air Traffic Control Tower (ATCT) on downwind, to receive their clearance back to their originating airport.

Contributing factors

  • cause Not used/operated
  • cause Flight crew
  • factor Flight crew

Conditions

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