- Date
- July 8, 2013, 17:00 local (21:00 UTC)
- Place
- Beaufort, NC
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N6651KGrumman Acft ENG Cor-Schweizer G-164B
- Defining event
- Landing-landing roll: Sys/Comp malf/fail (non-power)
- Weather
- Visual (VMC) · Day
- Status
- Completed · report March 13, 2014
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20130708017239A
- Case key
- 87427
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
A failure of the right brake for reasons that could not be determined because a postaccident examination of the brake could not be performed.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot was landing the airplane on a private airstrip to pick up a load of chemicals for another agricultural spraying flight. The pilot reported that the right brake felt "mushy" during the landing roll and that he pressed it to its maximum range (to the floor). The airplane began to veer to the left, and the pilot applied full power in an attempt to maintain control of the airplane; however, the left wingtip struck crops near the runway. Subsequently, the airplane turned to the left and came to rest in a ditch. The private airstrip was a 25-foot-wide by 2,000-foot-long paved runway with crops planted about 20 feet from the sides of the runway. The airplane was not made available for postaccident examination; however, the pilot noted that a new master cylinder and landing on a wider runway could have helped prevent this accident. A reason for the right brake failure could not be determined.
Factual narrative
On July 8, 2013, about 1700 eastern daylight time, a Grumman Aircraft G-164B, N6651K, was substantially damaged when it impacted crops and terrain while landing at a private airstrip near Beaufort, North Carolina. The private pilot was not injured. The airplane was owned by an individual and operated by Distant Farms under the provisions of Title 14 Code of Federal Regulations Part 137 as an aerial application flight. Visual meteorological conditions prevailed and no flight plan was filed for the local flight. According to the pilot, he was landing to pick up another load of chemicals. During the landing roll, the right brake felt "mushy" and it was pressed the maximum range to the floor. The airplane began to veer to the left and the pilot applied full power in an attempt to maintain control of the airplane, however, the left wingtip struck crops located near the runway. Subsequently, the airplane turned to the left and came to rest in a ditch. The private airstrip included a paved runway that was about 25-feet-wide and 2,000-feet-long. In addition, the crops were planted about 20 feet from the edge of the runway. According to Federal Aviation Administration (FAA) records, the pilot held a commercial pilot certificate for airplane single-engine land and helicopter. His most recent second-class medical certificate was issued on July 1, 2013. He reported 14,000 hours of total flight time, of which, 5,000 were in the same make and model as the accident airplane. The pilot reported flying for about 8 hours on the day of the accident. In addition, the pilot held an airframe and powerplant certificate with inspection authorization. According to FAA records, the airplane was manufactured in 1978, and registered to the pilot in 1996. The most recent annual inspection was completed on April 2, 2013, at a tach time of 3436.1. During the most recent annual inspection, the pilot/mechanic stated that he "serviced wheel, brake reservoirs, changed both batteries, replace brake pads, rebuilt pucks & master cylinders..." At the time of the accident, the airplane had accumulated 3535.8 total hours. A postaccident examination of the airplane was unable to be performed since the airplane was disposed of prior to an examination being scheduled. In the Operator/Owner Recommendation section of the NTSB Pilot/Operator Aircraft Accident/Incident Report, the pilot recommended that a new master cylinder and landing on a wider runway could have helped prevent this accident.
Aircraft
- Registration
- N6651K
- Reported as
- Grumman Acft ENG Cor-Schweizer G-164B
- Category
- Airplane
- Serial number
- 406B
- Built
- 1978
- Airframe hours
- 7,954
- Engine
- Garret TPE-331-25, 600 horsepower, turbo prop
- Damage
- Substantial damage
- Flight
- Aerial application · Part 137
- Airworthiness certificate
- Special, Restricted (Special)
- Last inspection
- Annual · March 6, 2013
- Departed
- NA · Beaufort, NC
- Destination
- NA · Beaufort, NC
- Airport
- NA · Private Airstrip, runway NA, 2,500 × 20 ft, grass/turf
- Equipment
- Stall warning system
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 60
- Injuries
- None
- Certificate
- Commercial
- Airplane ratings
- Single-engine land
- Medical
- Class 2, With waivers/limitations
- Last flight review
- February 1, 2013
- Seat
- Single
- Flight hours
- 14,000 total · 5,000 in this make and model · 14,000 as pilot in command · 120 in the last 90 days · 60 in the last 30 days · 8 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 180° at 8 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 88 °F, dew point 72 °F
- Altimeter
- 30.13 inHg
- Observed at
- EWN, 33 nm away
Docket · 5
The files NTSB released with the investigation on November 26, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.8 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.