SEA82FA052 · Cessna A152
Bremerton Aviation Incorporate Cessna A152 · Accident: near collision between aircraft during initial climb
From Bremerton National Airport (PWT) to Bremerton National Airport (PWT)
Event
- NTSB case
- SEA82FA052
- 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
- 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
- Instrument Meteorological Cond
Cessna A152
- Aircraft type
- Cessna 152
- 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
- N761QZ
- Operator
- Bremerton Aviation Incorporate
- Onboard fatalities
- Unknown
- Route
- From Bremerton National Airport (PWT), Bremerton, WATo Bremerton National Airport (PWT), Bremerton, 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
- Initial climb
- 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
- Near collision between aircraft
- 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 › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT TOOK OFF DOWNWIND AND AGAINST TRAFFIC IN MARGINAL WEATHER CONDITIONS. NO FLIGHT PLAN WAS FILED AND THERE WAS NO RECORD OF A WEATHER BRIEFING. DURING DEPARTURE, A NEAR-MISS OCCURRED BETWEEN N761QZ AND A LIGHT TWIN-ENGINE AIRCRAFT ON AN INSTRUMENT APPROACH TO THE AIRPORT. THE RENTAL OPERATOR CONTACTED THE PILOT ON UNICOM AND REQUESTED THAT HE OBTAIN A SPECIAL VFR CLEARANCE TO RETURN AND LAND. THE PILOT ACKNOWLEDGED. WHEN THE AIRCRAFT BECAME OVERDUE, A SEARCH WAS INITIATED. IT WAS FOUND WHERE IT CRASHED ON HEAVILY WOODED, RISING TERRAIN. THE TERRAIN SLOPED UPWARD ABOUT 40 DEGREES AND THE ELEVATION OF THE CRASH SITE WAS APPROXIMATELY 1000 FT MSL. THE PILOT WAS FOUND, DECEASED, ABOUT 1/2 MILE FROM THE WRECKAGE. TOXICOLOGICAL TESTS FOR ALCOHOL IN THE PILOT'S BLOOD AND URINE REVEALED .039 AND .139 PER CENT, RESPECTIVELY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA82FA052
- Event ID
- 20020917X02621
- Case number
- SEA82FA052
- 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: 74e00a25083d399d67e5d4e0c5eced13fc894b632a0df5d72598a21ce5ab4ea8; retrieved 2026-09-21T08:32:29.267Z.