- Manufacturer (registry)
- CONT MOTOR
- Model
- GIO-470SERIES
- Registry code
- 17034
- Installed in
- 8 registered aircraft
- Type
- Reciprocating
- Power
- 310 hp
Model codes come from the FAA registry’s reference file.
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 · 8
N181WWInternational Air Services Inc Trustee · Carson City, NVN189MWWilliamson Aviation Inc · Tullahoma, TNN303JANx Aviation LLC · Fredericksburg, VAN46880Miller San · New York, NYN6677YBrown Hunter L · Sulphur Rock, ARN8237DPts Inc · Wichita, KSN9025QVee Tails Of Flying Cloud Inc · Excelsior, MNN95BAKoontz Gregory Leonard · Crossville, TN
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 ('17034')
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 ('17034')
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 · 4
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 2 cases with NTSB’s older coding, defined in its coding manual.
NTSB ERA14FA232Accident · 1 fatalField investigationFinal reportNavion G · Hamilton Township, NJThe pilot's mismanagement of the onboard fuel supply, which resulted in fuel starvation to the engine and a subsequent loss of engine power. Contributing to the death of the right front passenger was the inadequate occupant restraint.NTSB LAX83LA467Accident · 1 fatalLimited investigationFinal reportde Havilland B-206 · Davenport, CAThe acft collided or ditched in the water while attempting to evade customs officials. Custom officials had been watching this acft and followed it from Mexico. After a touch and go landing at compton the acft left the los angeles area at 200 ft MSL trying to…NTSB MIA83LA032Accident · No injuriesLimited investigationFinal reportBeagle 206 · Near St. Cloud, FLMarijuana laden acft collided with trees during a landing attempt on a 2-lane paved road. Injuries presumed.NTSB LAX69D0170Accident · No injuriesClosedBeech J35 · Brawley, 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 ('17034')
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 ('17034')
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 · 11
Matched to this engine model through the registry, by N-number and event date, checked against the reported make and model.
Accident 20140509007199ANavion Navion G · Hamilton Townsh, NJOn may 9, 2014, at 2031 eastern daylight time, a Navion G, N2473T, was substantially damaged when it impacted trees and terrain in Hamilton township, new jersey, after a loss of engine power. The commercial pilot and one of the passengers were seriously…Incident 20081210856009IBeech A36 · Pinehurst/Sout, NC(-23) While being vectored onto and ILS approach, the pilot ran the before landing checklist and did not extend his gear when the checklist called for it. The approach was flown with a 40 to 50 knot tailwind with ground speeds reported by the pilot in excess…Incident 20060709027979IBag B2061 · Cairo, IL(-23) Aircraft departed runway 14 at Cairo, Illinois on post maintenance local flight. The pilot reported that shortly after takeoff he experienced a "loss of thrust" on the left engine. The pilot elected to make a precautionary landing off the airport due to…Incident 20040131002269IBag B2061 · Slaton, TX(-23) On January 31, 2004, at approximately 1630 CST, aircraft N87590, flown by pilot graeme l. cooper, experienced a nose gear collapse after landing at the Slaton Municipal Airport (F49), in Slaton, Texas. There were no injuries. The pilot was the sole…Incident 20031117031949IBeech A36 · Lumberton, NC(-23) According to the PIC and SIC statements at 3500 feet the aircraft was subject to sudden power and engine noise change. Crew coordination procedures were performed to find the fault of the power loss and engine noise change. Crew coordination procedures…Incident 20011026032599IAmtr Wichawk · Topeka, KS(-23) [privacy data omitted] taxied from the ga ramp to rwy 3 via taxiway "a" in his conventional gear biplane. As brakes were applied when the aircraft approached the hold short line of the departure runway, the aircraft nosed over. Damage was done to the…Incident 19940705026639IBeech J35 · Corona, CAPilot reported failed to extend gear for landing. Landed gear up.Incident 19921119052309IBeech A36 · Richmond, VAAlmost landed gear up. When propeller struck runway pilot pulled up. Lowered gear. Landed on same runway.Incident 19851126065339IBeech A36 · Whiteville, NCAircraft was landed with gear in the up position.Accident 19840914002949ABag B2061 · Davenport, CAFlew into a fog bank offshore while pursued by dea aircraft. Marijuana, pilots body and debris washed ashore later.Accident 19821122062489ABag B2061 · St Cloud, FLMarijuana loaded aircraft struck trees and crashed on attempted night landing on a road. Pilot fled scene.
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 ('17034')
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 ('17034')
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
No reports name this modelGeneral aviation reporting is voluntary.