FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA82FA032 · Cessna P210N

21 Jan 1982 · Boise, ID, United States

Cessna P210N · Accident: airframe, component or system failure en route

From Boise Air Terminal/Gowen Field (BOI) to North Las Vegas Airport (VGT)

Report a problem

Event

NTSB case
SEA82FA032
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
4 · 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 P210N

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
N4947K
Operator
Howard e Johnson · private individual
Onboard fatalities
Unknown
Route
From Boise Air Terminal/Gowen Field (BOI), Boise, IDTo North Las Vegas Airport (VGT), North Las Vegas, NV
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
Airframe, component or system failure
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 › Design stress limits of aircraft, exceeded
  • Pilot in command › Spatial disorientation
  • Vacuum system › Failure, total
  • Wing, spar › Overload

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

NTSB narrative

AFTER TAKEOFF WHILE CLIMBING THROUGH 10,000 FT MSL THE PILOT DECLARED AN EMERGENCY. THE PILOT STATED HE WAS HAVING VACUUM PROBLEMS AND WAS ON PARTIAL PANEL. SALT LAKE CITY ARTCC ANSWERED HIS REQUEST FOR GUIDANCE TO A VFR LANDING WITH NO GYRO VECTOR INSTRUCTIONS BACK TO BOISE. THE PILOT THEN STATED HE HAD A PROBLEM WITH THE TURN COORDINATOR AND THAT THE VACUUM PUMP WAS NOT OPERATING. AT 0856 THE AIRCRAFT DISAPPEARED FROM THE SALT LAKE CITY ARTCC AND BOISE APPROACH CONTROL RADAR SCOPES. NO FURTHER RADIO CONTACT WAS MADE WITH THE AIRCRAFT. THE WRECKAGE WAS FOUND 18 MILES SE OF BOISE AFTER HAVING IMPACTED THE GROUND AT A NEAR VERTICAL ANGLE, STRIKING THE NOSE AND LEFT WING FIRST. EXAMINATION OF THE DRY AIR VACUUM PUMP REVEALED PREIMPACT FAILURE DAMAGE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA82FA032
Event ID
20020917X02619
Case number
SEA82FA032
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: ca0bf2bc0e5652661acb2227487ed8b9b9356baa1cbe0e10c51673274595c9de; retrieved 2026-09-21T08:38:46.232Z.