13 Aug 2015: GRUMMAN G164 A — EASTERN FLYING SERVICE INC

13 Aug 2015: GRUMMAN G164 A (N5277) — EASTERN FLYING SERVICE INC

No fatalities • Trenton, NC, United States

Probable cause

The pilot's decision to land the airplane with a tailwind and his subsequent application of excessive braking, which resulted in a nose-over.

— NTSB Determination

Accident narrative

On August 13, 2015, about 1052 eastern daylight time, a Grumman G-164A, N5277, nosed over during landing at a private, unregistered airstrip near Trenton, North Carolina. The commercial pilot was not injured. The airplane sustained substantial damage to both wings, the empennage, and the fuselage. Visual meteorological conditions prevailed and no flight plan was filed for the local, aerial application flight. The airplane was owned and operated by Eastern Flying Service, Inc. under the provisions of Title 14 Code of Federal Regulations Part 137.

According to the pilot, the landing area was oriented in a west-northwest direction and landing in the east-southeast direction was not an option due to powerlines on the approach end and trees and a river on the east side. He further stated that, due to the short length of the landing surface, a balked landing was not an option. As the airplane approached the landing area from the east, after clearing the bordering 100-foot-tall trees, the pilot lowered the nose, and made a three-point landing in the turf portion of the landing area, just prior to the paved surface, as he had done for at least eight previous landings. He applied the brakes and reported that the pedal "pressure felt normal;" however, there was no braking action noted. While applying back pressure to the control stick, he subsequently released and reapplied the brakes and the airplane nosed-over, coming to rest inverted.

According to an eyewitness, the airplane had landed and that "no smoke" was emanating from the tires as they had observed on previous landings. The airplane continued forward and then "smoke" was observed coming from the tires, prior to the nose striking the pavement and the airplane nosing over.

According to another witness, they heard a "chirp" followed shortly by a "thud" sound. That witness described the "chirp" sound similar to "tires briefly sliding on pavement." However, the witness did not visually observe the accident.

According to a Federal Aviation Administration (FAA) inspector, the airplane came to rest inverted at the edge of a paved landing area. Numerous tire skid marks were noted on the paved portion of the landing area; however, it could not be conclusively determined which, if any, skid marks were from the accident flight. A divot was also noted in the paved surface, in the vicinity of the airplane, similar in dimensions as the propeller attach nut. One of the FAA inspectors that responded to the accident location examined the airplane's brakes and spun the wheels by hand. Another FAA inspector applied hand pressure to the brake pedals and no abnormalities or malfunctions were noted that would have precluded normal operation of the brake system.

The landing area was privately owned at the time of the accident. It consisted of a paved surface about 1,200 feet long and 15 feet wide and a turf area about 485 feet long on the east, or approach end, in relation to the accident flight. The landing area had trees located on the east side and a road that ran perpendicular to the runway on the west side, located about 30 feet beyond the paved surface. Photographs taken at the accident location revealed a powerline parallel to the road way; however, the powerline did not extend into the extended centerline of the landing area.

A review of surrounding airports, located within 20 miles of, and in various directions from, the accident location, revealed that the wind varied in direction between the northeast and east and the wind velocity varied between 3 and 10 knots. The recorded wind at an airport about 15 miles to the southwest, taken about 3 minutes after the accident, revealed the wind was from 090 degrees and 9 knots. The wind sampling included two hours prior and two hours following the accident.

Contributing factors

  • cause Pilot
  • cause Pilot
  • cause Incorrect use/operation
  • cause Effect on operation
  • cause Decision related to condition

Conditions

Weather
VMC, wind 090/09kt, 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.