The U.S. aircraft register, updated daily
Accidents · NTSB ERA15LA314 · Final report

Grumman G164 accident near Trenton, North Carolina, August 13, 2015

On August 13, 2015 at about 2:52 pm local time, a 1968 Grumman G164, registered N5277, was substantially damaged in an accident during landing (landing roll) near Trenton, North Carolina (Gene Powers airport). It was an aerial application (crop spraying) flight under agricultural flying rules (Part 137). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 13, 2015 · about 2:52 pm local time
Place
Trenton, North Carolina · Gene Powers · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Grumman G164 A, built 1968 · all G164s on the register
Registration
N5277 · no longer on the register · serial 566
Damage
Substantial damage
Flight
Aerial application (crop spraying) flight · agricultural flying rules (Part 137)

The NTSB's narrative final · quoted from the NTSB record

The commercial pilot reported that, following an agricultural application flight in the tailwheel-equipped airplane, he chose to land toward the northwest on a private landing area. He reported that he made this decision based on power lines on the approach end and that landing in that direction precluded the option of a balked landing; however, photographs taken at the accident scene revealed that no power line crossed the extended runway centerline. The pilot made a three-point landing and applied the brakes; however, he noted no braking action. The pilot then released and reapplied the brakes, and the airplane subsequently nosed over and came to rest inverted. A witness reported that, as the airplane was landing, he saw smoke coming from the tires. Postaccident examination of the brakes revealed no mechanical malfunctions or abnormalities that would have precluded normal operation. A review of recorded wind information from nearby airports indicated that the airplane likely landed with up to a 9-knot tailwind. Although numerous tire skid marks were noted on the paved landing area, it could not be determined which, if any, of those marks were caused by the accident airplane. However, given the witness statement indicating that he saw smoke coming from the tires after landing and the airplane's subsequent nose-over, it is likely that the pilot applied excessive braking action. Therefore, it is likely that the airplane was landing with excessive speed due to the tailwind and that the pilot subsequently applied excessive braking to slow the airplane before reaching the end of the runway, which resulted in the airplane nosing over and coming to rest inverted.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Nose over/nose down during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Incorrect use/operation
  • cause Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation
  • cause Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Decision related to condition

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,827.1 hours in all; 474.7 in this make and model; 408.2 in the last 90 days; 103.3 in the last 30 days; 1,697.8 as pilot in command
  • Last flight review: March 15, 2015
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: sngl
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection; 67 hours since
  • Maximum gross weight: 4,500 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: P&W R-1340-S3H1G (piston); 0 hours total
  • Operator: Eastern Flying Service INC

The flight

  • Departed from: PVT Trenton NC
  • Destination: PVT Trenton NC
  • Flight plan: none
  • Runway UNK, 1,700 ft by 15 ft

Weather at the time

  • Light: daylight
  • Wind: from 090° at 9 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 3,100 ft
  • Temperature: 82°F (28°C), dew point 63°F (17°C)
  • Altimeter: 30.09 inHg
  • Observation at 2:55 pm from KOAJ, 15 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

9 documents, released by the NTSB on February 24, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N5277 the same tail number, which may have belonged to a different aircraft at the time

1994-05-26CHI94DTG01 · accident near La Moure, ND · substantial damage · no injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.