WPR22LA092 · Cessna T207
Rugby Aviation Cessna T207 · Accident: runway excursion during landing
From Bellingham International Airport (KBLI) to Crane Island, WA (private airstrip)
Event
- NTSB case
- WPR22LA092
- 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
- Event fatalities
- Unknown
- 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
Cessna T207
- Aircraft type
- Cessna 207
- 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
- N684S
- Operator
- Rugby Aviation
- Onboard fatalities
- Unknown
- Route
- From Bellingham International Airport (KBLI), Bellingham, WATo Crane Island, WA (private airstrip)
- Aircraft age
- About 53 years (built 1969)
- 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
- 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
- Runway excursion
- 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 › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the airplane reported that, while landing on a private grass 1500 ft. runway, the airplane landed “slightly long and fast.” During the landing roll, flaps were immediately raised, and brakes were applied, however the braking was ineffective on the wet grass. The safety pilot called for a go-around. The pilot was concerned there was insufficient room to accelerate and elected to decelerate instead of attempting a go-around. The airplane exited the departure end of the runway, impacted terrain, and came to rest upright. The airplane’s lower fuselage was substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to obtain a proper touch down location on a wet grass runway, resulting in a runway overrun and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA092
- Event ID
- 20220208104614
- Case number
- WPR22LA092
- 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, coordinates, cause areas. 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: 5233a339e378c62f650bb200c9a4fb2f3a02865ed12eab81324ad77ce8b191a3; retrieved 2026-09-16T14:56:41.475Z.