US Aviation Grumman G-159C incident
Grumman G-159C · Incident: loss of control on ground/water during landing
From Sheridan County Airport (SHR) to an unrecorded destination
Event
- NTSB case
- DEN82IA103
- 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
- Incident
- 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
- 0
- 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
- Airline
- 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 G-159C
- Aircraft type
- Grumman G-159
- 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
- N159AN
- Operator
- U.S. Aviation
- Onboard fatalities
- Unknown
- Route
- From Sheridan County Airport (SHR), Sheridan, WYTo not recorded
- Aircraft age
- Not recorded
- 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 121: Air Carrier
- 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
- First occurrenceThe 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
- Loss of control on ground/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Copilot/second pilot › Directional control, not maintained
- Pilot in command › Supervision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT WAS ON A SCHEDULED, DOMESTIC, PAX FLT. THE COPLT WAS THE COMPANY'S CHIEF PLT AND WAS FLYNG THE ACFT FROM THE LEFT SEAT. HE WAS UNDER SUPERVISION OF THE PILOT-IN-COMMAND (PIC) WHO WAS IN THE RT SEAT. DRG ARRIVAL, THE CREW ELECTED TO MAKE A LOCALIZER-ONLY APCH TO RWY 33 WHICH WAS WET. JUST PRIOR TO LNDG, THE WIND WAS REPORTED FROM 280 DEG AT 15 KNTS. (ACCORDING TO AN OFFICIAL WX OBS AT 1736 MDT, THE WIND WAS FROM 290 DEG AT 17, GSTG 25 KTS.) REPORTEDLY, THE LNDG APCH & TCHDWN WERE NORMAL. AT APRX 90 KTS, GROUND FIND FINE PITCH (GFP) WAS SELECTED & THE ACFT VEERED TO THE LEFT. NOSE WHL STEERING & RUDDER WERE RPRTD AS NIL. THE PIC ASSUMED CONTROL, BUT THE ACFT WENT OFF THE LEFT SIDE OF THE RWY BFR HE WAS ABLE TO STOP THE SWERVE AND PARALLEL THE RWY. THERE WAS NO DNG OR INJURY. DURING AN INVESTIGATION, THE LEFT ENGINE WAS FOUND TO IDLE AT 8000 RPM, THE RGT ENGINE IDLED AT 9000 RPM. THE RECOMMENDED IDLE SPEED WAS 6500 TO 7500 RPM.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN82IA103
- Event ID
- 20020917X03238
- Case number
- DEN82IA103
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, damage. 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: e48667190b6032433b53cca7d929183250d7e28a52765ae72679d22a0a1e365f; retrieved 2026-09-18T21:09:14.090Z.