FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA99LA140 · Cessna T210J

31 Jul 1999 · Sequim, WA, United States

Cessna T210J · Accident: overrun during landing

From Jefferson County International Airport (0S9) to an unrecorded destination

Report a problem

Event

NTSB case
SEA99LA140
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
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
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 T210J

Aircraft type
Cessna 210
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
N821SB
Operator
Judith J. Harris-Redshaw · private individual
Onboard fatalities
Unknown
Route
From Jefferson County International Airport (0S9), Port Townsend, WATo 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 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
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
Overrun
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

  • Pilot in command › Compensation for wind conditions, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot overflew the 1,600 foot asphalt runway to determine the wind direction before landing. After determining a crosswind would be present for either runway, the pilot chose to land to the east. As the aircraft touched down, the pilot realized '...that the wind had changed directions and was now from the west.' With the westerly wind, the pilot was landing with a tailwind that she estimated at 10 knots gusting to 20 knots. Although she was aware that she may not get the aircraft stopped prior to reaching the end of the runway, she elected not to attempt a go-around because of the possibility of impacting obstructions just off the departure end. The pilot was unable to stop the aircraft before it departed the end of the runway and collided with a berm.

Probable cause

The pilot's failure to adequately compensate for the changing wind conditions. Factors include a berm located off the east end of the runway and a tailwind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA99LA140
Event ID
20001212X19389
Case number
SEA99LA140
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. 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: 9592155aa3c639e5e649b4c2cdda6003ff0122d4ffd946523470be8009f62b9e; retrieved 2026-09-22T14:21:52.091Z.