CEN09CA520 · Grahn J/Grahn G PITTS S2S
Grahn J/Grahn G PITTS S2S · Accident: abnormal runway contact during landing
From Garfield County Regional Airport (KRIL) to Garfield County Regional Airport (KRIL)
Event
- NTSB case
- CEN09CA520
- 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
- Accident
- 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
- Unknown
- 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
- General aviation
- 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
Grahn J/Grahn G PITTS S2S
- Aircraft type
- Grahn J/grahn PITTS S2S
- 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
- N540S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Garfield County Regional Airport (KRIL), Rifle, COTo Garfield County Regional Airport (KRIL), Rifle, CO
- 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 91: General Aviation
- 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
- Defining eventThe 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
- Abnormal runway contact
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the Federal Aviation Administration (FAA), the pilot had just completed practice for his air show performance and was landing on runway 26. The pilot stated that he landed fast and while braking to make an intersection, the brakes became hot and the right brake began to fade. The airplane began to track to the left and the pilot steered the airplane between two taxi lights. The airplane impacted a taxiway sign, breaking the right lower right inboard spar. The pilot did not see the sign prior to impact. An examination of the airplane, conducted by the FAA, revealed no mechanical anomalies.
Probable cause
The pilot's excessive landing speed and subsequent excessive brake application which resulted in a loss of control and impact with an airport sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09CA520
- Event ID
- 20090813X73143
- Case number
- CEN09CA520
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 0a9046c5b9b07008e8a922f60fda823fd9650dfdeaaeae82d314ac1cfb095168; retrieved 2026-09-15T12:47:57.374Z.