Grahn J/Grahn G PITTS S2S accident near Rifle, Colorado, August 13, 2009
On August 13, 2009 at about 8:30 pm local time, a Grahn J/Grahn G PITTS S2S, registered N540S, was substantially damaged in an accident during landing (landing roll) near Rifle, Colorado (Garfield County Regional Airpo). It was an air show or air race flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's excessive landing speed and subsequent excessive brake application which resulted in a loss of control and impact with an airport sign.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 13, 2009 · about 8:30 pm local time · cases in 2009
- Place
- Rifle, Colorado · Garfield County Regional Airpo · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Grahn J/Grahn G PITTS S2S
- Registration
- N540S · registry record · serial 009
- Damage
- Substantial damage
- Flight
- Air show or air race flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Abnormal runway contact during landing (landing roll) defining event
- Sys/Comp malf/fail (non-power) during landing (landing roll)
- Runway excursion during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Incorrect use/operation
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Surface speed/braking › Not attained/maintained
- Aircraft › Aircraft systems › Landing gear system › Brake › Capability exceeded other cases naming the landing gear
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
Pilot
- Certificate: airline transport pilot, flight instructor, commercial pilot, flight engineer
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 8,365 hours in all; 708 in this make and model; 54 in the last 90 days; 20 in the last 30 days; 4,380 as pilot in command
- Last flight review: February 20, 2009
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: ctr
- Injury: no injuries
The aircraft
- Airframe total time: 1,527 hours
- Last inspection: condition inspection, June 15, 2009
- Maximum gross weight: 1,550 lb
- Seats: 1
- Landing gear: fixed
- Engine: Lycoming IO-540-S1A5 (piston); 0 hours total
The flight
- Departed from: KRIL Rifle CO at 7:50 pm
- Destination: KRIL Rifle CO
- Flight plan: none
- Runway 26, 7,011 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 190° at 13 knots, gusting 20
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 37°F (3°C)
- Altimeter: 30.17 inHg
- Observation at 8:53 pm from KEEO, 32 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on August 25, 2009. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N540S the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N540S on the register today · the tail number may have moved to another aircraft since
- Engine: Lycoming IO-540-S1A5 10 aircraft carry this series today · as the NTSB recorded it
- Rifle Garfield County · nearest airport
- Accidents and incidents in Colorado 2,860 since 1982 · 383 in the last ten years
- Colorado 7,490 aircraft registered
- Other NTSB records under N540S 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN09CA520.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
