- Manufacturer (registry)
- CONT MOTOR
- Model
- R-975 SER
- Registry code
- 17037
- Installed in
- 12 registered aircraft
- Type
- Reciprocating
- Power
- 550 hp
The registry names only the engine series, so ADs for every model in the series are matched.
On this page
Airworthiness directives that may apply · 0
ADs whose products match this engine model. Each AD’s applicability may narrow it by serial number, part number or configuration.
No ADs matched this model
Registered aircraft · 12
N164TNBuntings Dusting Inc · Berlin, MDN211ERMorgans Flying Service LLC · Morse, LAN3362Otto Lawrence G · Kalispell, MTN4420MJohnson Capital LLC · Colleyville, TXN6565KHouston Ag Flying Sev Inc · Owensboro, KYN6718KScott Flying Service Inc · Bono, ARN6720KScott Flying Service Inc · Bono, ARN6730KBasin Aviation Inc · Rio Oso, CAN6745KDc Applicator · Brentwood, CAN6798QGustin Aviation Inc · Lewiston, IDN6808QChurch Street Holding LLC · Kaplan, LAN6822QAlbright Frank E · Elba, AL
Query with SQL
duckdb -csv -c "SELECT n_number, serial_number, year_manufactured, status, registrant_name, registrant_city, registrant_state
FROM 'https://openairdocs.org/data/latest/faa_aircraft_registration.parquet'
WHERE engine_model_code IN ('17037')
ORDER BY n_number"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT n_number, serial_number, year_manufactured, status, registrant_name, registrant_city, registrant_state
FROM 'https://openairdocs.org/data/latest/faa_aircraft_registration.parquet'
WHERE engine_model_code IN ('17037')
ORDER BY n_numberRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB investigations · 14
Aircraft matched to this engine model through the registry, by N-number and event date, checked against the reported serial number, make and model.
Of 1 case NTSB coded with a defining event. All defining events
Findings NTSB made part of the probable cause. A case can have several. All findings
Of 11 cases with NTSB’s older coding, defined in its coding manual.
NTSB WPR10LA048Accident · 3 fatalLimited investigationFinal reportPiasecki/Pike PV-18 · Adelanto, CAThe pilot’s failure to maintain clearance from powerlines during en route flight.NTSB DEN06CA081Accident · Minor injuriesData collectionFinal reportGrumman G-164B · Dighton, KSThe broken rocker arm boss causing the number 1 cylinder exhaust valve to stay closed and subsequently the engine failed. A factor contributing to the accident was the soft field the airplane set down in.NTSB FTW02LA132Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Gillett, ARthe pilot's failure to maintain directional control on landing. A contributing factor was the high vegetation.NTSB DEN01LA163Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164A · Parowan, UTthe pilot's failure to maintain adequate airspeed which resulted in an inadvertent stall/mush into terrain. Contributing factors were the pilot's diverted attention, the rising terrain, and the high density altitude weather condition.NTSB FTW98LA164Accident · No injuriesLimited investigationFinal reportGrumman-Schweizer G-164B · Tuckerman, ARThe pilot's failure to maintain aircraft control. Factors were the wet and soft runway conditions.NTSB FTW92LA144Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Mamou, LAThe engine failure for undetermined reasons. A factor was the lack of suitable terrain onto which the ensuing forced landing could be executed.NTSB CHI90LA219Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Columbus, NEStanding water on the approach end of the runway.NTSB FTW89DRA06Accident · No injuriesFinal reportGrumman G-164B · Lissie, TXA bird strike which resulted in foreign object damage to the engine compressor. A berm and the lack of suitable terrain for a forced landing were contributing factors.NTSB SEA87LA067Accident · No injuriesLimited investigationFinal reportGrumman G164B · Reubens, IDDuring takeoff run the aircraft veered to the right of the runway, struck a ditch, and then nosed over inverted. The pilot found that the right dowel pin on the right main gear had broken. The reason for the failure could not be determined.NTSB LAX84LA474Accident · No injuriesLimited investigationFinal reportGrumman 164A · Goodyear, AZPlt reported pwr loss occurred during night aerial application. Acft nosed over during forced landing in crop field. Investigation failed to reveal any evidence of a mechanical failure/malfunction. Engine was test run to extent permitted by damage and no…NTSB MKC84LA255Accident · No injuriesLimited investigationFinal reportGrumman G-164B · Marianna, ARThe landing gear contacted the bean crop which was being sprayed with sodium chlorate and the acft nosed over.NTSB SEA84LA133Accident · Minor injuriesLimited investigationFinal reportGrumman G-164B-450 · Pullman, WAAfter making a swath run, the acft entered a steep turn with an airspeed of about 75 mph. According to two witnesses, the eng lost power & then the acft crashed. The plt was unable to remember what had happened from the time he entered the turn until he…NTSB FTW81DRJ13Accident · No injuriesClosedGrumman G-164B · Mer Rouge, LANTSB OAK76DVG70Accident · Minor injuriesClosedGrumman G-164A · Butte City, CA
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.engine_model_code IN ('17037')
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.engine_model_code IN ('17037')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
FAA incident reports · 15
Matched to this engine model through the registry, by N-number and event date, checked against the reported make and model.
Accident 20091107021769APiasec PV18 · Adelanto, CAThe aircraft was an experimental exibition being flow from Adelanto, CA. To flabob, CA. When it experienced an unknown problem in flight, and it contacted the static line of a transmission tower, approximately 187 feet AGL. The helicopter descended rapidly…Accident 20060601013309AScwzer G164B · Dighton, KS(-23) The commercial aerial applicator was lifting off just past mid-field from runway 35 at his home base airport when the engine sputtered twice and quit. The pilot was able to land on the runway but the aircraft continued approximately 200 feet past the…Accident 20020429009289AScwzer G164B · Tichnor, AR(-23) On April 29, 2002, approximately 0810 central daylight time, a grumman-schweizer, G-164-B agricultural airplane, N6718K, sustained substantial damage when it nosed over while landing near gillett, Arkansas. The commercial pilot, sole occupant of the…Accident 20010927027399AScwzer G164A · Parowan, UT(.19) On September 27, 2001, at approximately 0900 mountain daylight time, a grumman-schweizer G-164A, N9925, was substantially damaged while maneuvering during aerial applicating near Parowan, Utah. The commercial pilot, the sole occupant in the airplane,…Accident 19980325004239AScwzer G164B · Tuckerman, ARAcft ran through a mud hole on landing and flipped over, Tuckerman, AR. (.4)during the landing roll, the right main landing gear dropped into a mud hole covered by 6 inch tall bermuda grass. The tire pushed up the mud instead of rolling through the hole, and…Accident 19920530017209AScwzer G164B · Mamou, LALost power on climbout after engine belched black smoke. Nosed over landing in water in muddy rice field.Accident 19900809031829AScwzer G164B · Columbus, NELanded on irrigation flooded runway and flipped over. Reported tall grass hid water until landing committed.Accident 19890601014249AScwzer G164B · Lissie, TXBird strike near air intake injested into engine caused flameout and nosed over on forced landing.Accident 19870319008059AScwzer G164B · Reubens, IDVeered off runway on takeoff and nosed over in a ditch. Dowel pin on right main gear broke. Allowed wheel turnout.Accident 19840908047769AScwzer G164A · Goodyear, AZEngine lost power resulting in forced landing. Aircraft damage substantial. Cause of power loss undetermined.Accident 19840816041509AScwzer G164B · Marianna, ARAg aircrafts wheels touched milo crop during a spray run. Aircraft flipped over.Accident 19840614026519AScwzer G164B · Pullman, WAWitnesses heard engine stop. Ag aircraft struck rising terrain in a steep bank. No engine defects found.Accident 19810428020419AGrumav G164B · Mer Rouge, LADownwind takeoff. Full load, warm day, premature liftoff. Struck wires on climbout.Incident 19790621016699IGrumav G164B · Walla Walla, WAPlane caught fire during attempted engine start. Carburetor float was stuck open.Accident 19760508011289AGulstm G164C · Butte City, CACarb accl pump stem,pn NAY9E1 and nut,pn P1229 not safetied. Lnd in rice fld.
Query with SQL
duckdb -csv -c "SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE engine_model_code IN ('17037')
ORDER BY event_date DESC, report_number DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE engine_model_code IN ('17037')
ORDER BY event_date DESC, report_number DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
Service difficulty reports · 1
Query with SQL
duckdb -csv -c "SELECT sdr_id, difficulty_date, n_number, aircraft_make, aircraft_model, part_name, part_condition, jasc_code, discrepancy FROM 'https://openairdocs.org/data/latest/faa_service_difficulty_report.parquet' WHERE engine_model_key = 'R975' ORDER BY difficulty_date DESC"
Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT sdr_id, difficulty_date, n_number, aircraft_make, aircraft_model, part_name, part_condition, jasc_code, discrepancy FROM 'https://openairdocs.org/data/latest/faa_service_difficulty_report.parquet' WHERE engine_model_key = 'R975' ORDER BY difficulty_date DESC
Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.