SEA04FA083 · Cessna 170B
Cessna 170B and Cessna 210J · Accident: midair collision en route
Event
- NTSB case
- SEA04FA083
- 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
- 1 · 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
Aircraft 1 · Cessna 170B
- Aircraft type
- Cessna 170
- 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
- N3510D
- Operator
- Ghyrn E. Loveness · private individual
- Onboard fatalities
- Unknown
- Route
- From Roseburg Regional Airport (RBG), Roseburg, ORTo Tacoma Command Post Heliport (WA69), Vashon, WA
- 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
- En route · cruise
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Cessna 210J
- 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
- N3329S
- Operator
- Scott C. Devlin · private individual
- Onboard fatalities
- Unknown
- Route
- From Grove Field (1W1), Camas, WATo Seattle Paine Field International Airport (PAE), Everett, WA
- 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
- En route · cruise
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Visual lookout, not obtained/maintained
- Pilot of other aircraft › Visual lookout, not obtained/maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
At 2038:10, a Cessna 170B and a Cessna 210J collided in-flight about 5 miles southeast of Tenino, Washington, at 3,000 feet mean sea level (about 2,700 feet above ground level). The Cessna 170B, flown by a private pilot, sole occupant of the airplane, was transponder equipped squawking code 1200 and emitting Mode C altitude information. The Cessna 170B had just descended from 7,500 feet msl and was leveling off at 3,000 feet on a magnetic heading of 322 degrees when the collision occurred. The pilot of the Cessna 170B, whose engine was separated from the airplane as a result of the collision, was able to maintain control of the airplane and succeeded in making a forced landing to an open field. The pilot of the Cessna 210J, also the sole occupant, was not emitting a transponder code, and therefore no altitude or other identifying information was available. However, a radar target was observed to the left and on a collision course with the Cessna 170B, and is assumed to have been the Cessna 210J; there were no other aircraft observed in the immediate vicinity. At 2036:11, the aircraft were approximately 3 1/2 nautical miles apart, the Cessna 210J oriented on a heading of north, while the Cessna 170B was on a magnetic heading of 309 degrees. At 2036:34, both aircraft were still on their respective headings, however, their lateral separation had diminished by 3/4 of a mile; the airplanes were now 2 3/4 miles apart. At 2036:58, lateral separation was reduced by 1/2 mile to 2 1/4 miles, and at 2037:22 lateral separation was further reduced to 1 1/4 miles. At 0337:46, 24 seconds prior to the collision, radar data indicates the aircraft were separated by a lateral distance of approximately 3,300 feet. Based on scratch marks and paint transfer signatures observed on both aircraft, as well as an estimated speed of the overtaking Cessna 210J being 150 knots and the GPS readout speed of the Cessna 170B of 113 knots, calculations revealed a closure speed of 41 knots, and a collision angle of 8 degrees. A calculated convergence angle of 22 degrees was determined for the Cessna 210J and 150 degrees for the Cessna 170B. It was concluded that based on the Cessna 210J's convergence angle and pilot's unobstructed forward field of vision, the Cessna 210J pilot should have been able to detect the presence of the Cessna 170B using normal visual scanning procedures consistent with visual flight rule (VFR) operations.
Probable cause
The other pilot's failure to maintain an adequate visual lookout during cruise flight, which resulted in a midair collision between the two airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04FA083
- Event ID
- 20040526X00672
- Case number
- SEA04FA083
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-05-17.
- API snapshot SHA-256: f0469f8610743c6067bcb9e8185408ada9b436373c0f16e275aede27d25b1926; retrieved 2026-09-20T18:28:46.821Z.