SEA93FA031 · Beech S35
Springville Flying Club Beech S35 · Accident: in flight collision with object during initial climb
From an unrecorded airport to Provo Municipal Airport (PVU)
Event
- NTSB case
- SEA93FA031
- 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
Beech S35
- Aircraft type
- Beechcraft 35
- 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
- N8634Q
- Operator
- Springville Flying Club
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Provo Municipal Airport (PVU), Provo, UT
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s); Wire, transmission
- 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 › Clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE INSTRUMENT RATED PILOT FILED AN IFR FLIGHT PLAN AND WEATHER BRIEFED FOR A ROUND TRIP FLIGHT FROM PROVO, UTAH, TO REXBURG, IDAHO, AND RETURN. UPON ARRIVAL AT REXBURG THE PILOT'S SON (WHO DISEMBARKED WITH A SECOND PASSENGER) REQUESTED THAT HIS FATHER REMAIN OVERNIGHT. THE PILOT RESPONDED THAT THE PLANE WOULD BE TOO HARD TO START AND THAT HE HAD A CLASS TO TEACH IN THE MORNING. AFTER A BRIEF STOPOVER, THE AIRCRAFT DEPARTED REXBURG AND THERE WAS NO EVIDENCE THAT THE PILOT ACTIVATED HIS IFR FLIGHT PLAN FOR THE RETURN LEG. A CESSNA 310 WAS ON AN IFR APPROACH INTO REXBURG DURING THE TIME OF THE ACCIDENT. LOW CEILINGS AND SNOW WERE REPORTED AT THE REXBURG AIRPORT AND ACCIDENT SITE, AS WELL AS DARK NIGHT ENVIRONMENTAL CONDITIONS. THE AIRCRAFT IMPACTED TREES AT A POINT APPROXIMATELY 23 FEET ABOVE GROUND IN A WINGS LEVEL ATTITUDE. IT THEN IMPACTED THE GROUND SHEDDING APPROXIMATELY 8 INCHES OF PROPELLER TIP BEFORE BECOMING AIRBORNE AGAIN, WHEREUPON IT IMPACTED POWER LINES AND THEN TERRAIN WITH ITS ENGINE ULTIMATELY COMING TO REST 1324 FEET BEYOND THE TREE IMPACTS.
Probable cause
THE PILOT IN COMMAND'S FAILURE TO MAINTAIN CLEARANCE WITH OBJECTS/TERRAIN. FACTORS CONTRIBUTING TO THE ACCIDENT WERE LOW CEILINGS, SNOW, DARK NIGHT CONDITIONS, TREES, IMPROPER PREFLIGHT PLANNING AND SELF INDUCED PRESSURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93FA031
- Event ID
- 20001211X16100
- Case number
- SEA93FA031
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1992-11-30.
- API snapshot SHA-256: 853f9c50c36fd32ab1e1f1ce255082f78987d817865239e8369ce99c79e412e6; retrieved 2026-09-21T00:47:38.996Z.