15 Mar 2010: BRITTEN-NORMAN BN-2A-21 — Servant Air

15 Mar 2010: BRITTEN-NORMAN BN-2A-21 (N663SA) — Servant Air

No fatalities • Kodiak, AK, United States

Probable cause

The pilot's failure to maintain clearance from rising terrain during takeoff resulting in collision with trees.

— NTSB Determination

Accident narrative

On March 15, 2010, about 1230 Alaska daylight time, a Britten-Norman BN-2A-21 airplane, N663SA, sustained substantial damage following a loss of control and impact with terrain during takeoff initial climb at the Kodiak Airport, Kodiak, Alaska. The airplane was being operated by Servant Air, Kodiak, as a visual flight rules (VFR) passenger flight under Title 14, CFR Part 135, when the accident occurred. The airline transport pilot and one passenger received serious injuries, and the second passenger received minor injuries. Visual meteorological conditions prevailed, and company flight following procedures were in effect. The flight was bound for Old Harbor, Alaska.

During a telephone conversation with the National Transportation Safety Board (NTSB) investigator-in-charge (IIC) on March 17, an FAA air safety inspector who interviewed witnesses at the airport, said one witness who was familiar with the Britten-Norman airplane said he saw the airplane at full power attempting to out climb the terrain at the end of the runway, before it descended into the trees. The witness reported that the right wing of the airplane struck the trees first, and then rolled left, striking trees with its left wing, and then continued its descent into the trees.

In a written statement to the NTSB dated March 23, the pilot said that the wind was reported as from 290-300 degrees, at 15 knots, gusting to 27 knots, and he chose to make an intersection takeoff on runway 25 at the intersection of runway 25 and runway 29. He said his airspeed did not develop as quickly as he had anticipated. The pilot reported that with his airspeed lagging and poor climb performance, he realized the airplane was not going to clear the ridge at the end of the runway. He said he initiated a right descending turn to maintain his airspeed, and flared for impact with the trees. The statement also indicated that there were no mechanical problems with the airplane prior to the accident.

Contributing factors

  • cause Capability exceeded
  • cause Pilot
  • Effect on equipment
  • Contributed to outcome

Conditions

Weather
VMC, wind 300/21kt, vis 7sm

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.