# NTSB FTW98LA161: Grumman G-164, N617Y, St. Joseph, LA, March 28, 1998 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: March 28, 1998, 15:30 local (21:30 UTC) - Place: St. Joseph, LA - Coordinates: 31.949645, -91.37059 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=31.9496&lon=-91.3706&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report December 8, 1998 - Report: Approved by Office Director - NTSB case key (mKey): 20562 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=FTW98LA161 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/20562/pdf - Page: https://openairdocs.org/ntsb/FTW98LA161 ## Probable cause The pilot's failure to maintain clearance from the trees. A factor was the lack of suitable terrain for the ensuing forced landing. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with object, maneuvering - aerial application - object - tree(s) - clearance - not maintained, pilot in command (cause) - Forced landing, emergency descent/landing - In flight collision with terrain/water, emergency landing - terrain condition - drop-off/descending embankment - terrain condition - none suitable (contributing factor) - Nose over, emergency landing ## Analysis Following three uneventful aerial application flights, the pilot removed the biplane's cockpit side windows. While completing the first pass of the fourth flight, the pilot 'noticed the plane did not perform as it had previously.' As he turned the airplane to begin the second pass, it settled into the trees bordering the field being sprayed. While in the trees, the pilot advanced the propeller and throttle controls and made an unsuccessful attempt to dump his load of herbicide. Upon reaching the edge of the trees, the pilot 'nosed the aircraft over to land in a small field before hitting the wire across the road.' As he flared to land, the airplane impacted the road embankment. Subsequently, the airplane nosed over, came to a stop in the inverted position, and began to burn. The postcrash fire consumed the fuselage, empennage, and the upper and lower right wings. ## Factual narrative On March 28, 1998, approximately 1530 central standard time, a Grumman G-164 agricultural airplane, N617Y, impacted terrain during a forced landing following an in-flight collision with trees while maneuvering near St. Joseph, Louisiana. The airplane, which was registered to and operated by the pilot, was destroyed. The commercial pilot, the sole occupant, sustained serious injuries. No flight plan was filed and visual meteorological conditions prevailed for the Title 14 CFR Part 137 local aerial application flight. The pilot reported that the airplane performed "normally" during the first three flights of the day. Prior to the fourth flight, he "removed the side windows of the cockpit." While completing the first pass of the fourth flight, the pilot "noticed the plane did not perform as it had previously." As he turned the airplane to begin the second pass, it "began to settle into the trees" bordering the field being sprayed. "While in the trees," the pilot advanced the propeller and throttle controls and attempted to dump his load of herbicide; however, he "was hitting [the] spray handle instead of [the] dump handle." Upon reaching the edge of the trees, the pilot "nosed the aircraft over to land in a small field before hitting the wire across the road." As he flared to land, the airplane "hit the embankment next to the road." The airplane "flipped across the road," came to a stop in the inverted position, and began to burn. The post-crash fire consumed the fuselage, empennage, and the upper and lower right wings of the biplane. According to FAA records, when the pilot's most recent medical certificate was issued on July 31, 1997, he reported that he had accumulated 15,300 total flight hours of which 300 hours were in the last 6 months. ## Aircraft - Registration: [N617Y](https://openairdocs.org/deregistered/N617Y-1998-11-09), registration cancelled 1998-11-09, S/N 232 (OpenAirDocs) - Reported make and model: Grumman G-164 - Registry model: [Grumman G-164](https://openairdocs.org/model/grumman-g-164) (registry code 3952702) (OpenAirDocs) - Category: Airplane - Serial number: 232 - Airframe hours: 11362 - Engines: P&W R-985 450 horsepower reciprocating - Damage: Destroyed - Fire: On-Ground - Flight: Aerial application, Part 137 - Registered owner: Phil Dear - Airworthiness certificate: Special, Restricted (Special) - Last inspection: Annual, July 21, 1997, 344 hours before ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 63; commercial; airplane ratings: single-engine land, multi-engine land; medical: class 2, valid medical--w/ waivers/lim; seat: center; flight hours: 15,300 total ## Weather - Conditions: Visual (VMC), Day - Wind: 180° at 8 knots - Visibility: 5 statute miles - Temperature: 70 °F ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19980328004499A](https://openairdocs.org/incident/19980328004499A), Mar 28, 1998: Scwzer G164, St Joseph, LA, Destroyed. Acft was involved in aerial applic when it turned, clipped trees, crashed in field, burned, st jospeh, LA. (.4)following three uneventful aerial application… ## Other investigations on N617Y (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB OAK66F0266](https://openairdocs.org/ntsb/OAK66F0266), Apr 21, 1966: Grumman G-164 (N617Y), Richvale, CA, substantial damage From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.