US Aviation Gulfstream G159-C incident
Gulfstream G159-C · Incident on approach
From Sheridan County Airport (SHR) to College Park, MD
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DEN82IA049
- 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
Gulfstream G159-C
- Aircraft type
- Gulfstream G159
- 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
- N857H
- Operator
- U.S. Aviation
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Sheridan County Airport (SHR), Sheridan, WYTo College Park, MD
- 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
- Approach · VFR pattern base
- 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
- Miscellaneous/other
- 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 › Incapacitation
Approximate · Estimated position: the centre of Denver, CO, the place the record names. Not the accident site.
NTSB narrative
ON FINAL APPROACH AFTER A NORMAL FLIGHT, THE COPILOT BECAME INCAPACITATED WHILE READING THE FINAL APPROACH CHECKLIST. THE CAPTAIN CONTINUED THE APPROACH AND MADE AN UNEVENTFUL LANDING. AFTER THE PASSENGERS HAD DEPLANED, THE COPILOT SUFFERED A SEIZURE WHILE HE WAS BEING HELPED DOWN THE STEPS BY THE CAPTAIN AND THE FLIGHT ATTENDANT. HE WAS TRANSPORTED TO THE HOSPITAL WHERE TESTS DETERMINED THAT HE HAD A CALCIUM DEPOSIT BEHIND THE RIGHT EAR THAT WAS APPLYING PRESSURE TO THE BRAIN. A CHEMOTHERAPY PROGRAM EVENTUALLY RESOLVED THE PROBLEM. THE COPILOT HAD RECEIVED HIS LAST CLASS I MEDICAL EXAMINATION TWO MONTHS PRIOR TO THE INCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN82IA049
- Event ID
- 20020917X01989
- Case number
- DEN82IA049
- 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: 8a2055bf95a434e6bb09fd7b048f1c56843692d8ebb27b5e710b72d51980bc7b; retrieved 2026-09-18T21:11:05.509Z.