ERA13LA318 · Grumman Acft ENG COR-Schweizer G-164B
Grumman Acft ENG COR-Schweizer G-164B · Accident: system/component malfunction/failure (non-power) during landing
From Beaufort, NC to Beaufort, NC
Event
- NTSB case
- ERA13LA318
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Grumman Acft ENG COR-Schweizer G-164B
- Aircraft type
- Grumman G-164
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N6651K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Beaufort, NCTo Beaufort, NC
- Aircraft age
- About 35 years (built 1978)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 137: Agricultural
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA318
- Event ID
- 20130709X23614
- Case number
- ERA13LA318
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e6883f6d393e08b5d1af9d9d50d594df53ef2e0f84d4d16c1bc38c9c619653dc; retrieved 2026-09-15T22:10:15.241Z.