FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN82DA042 · Beech A36TC

12 Mar 1982 · Boulder, CO, United States

Beech A36TC · Accident: undershoot on approach

From Jackson, WY to Scottsdale, AZ

Report a problem

Event

NTSB case
DEN82DA042
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

Beech A36TC

Aircraft type
Beechcraft 36
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
N3738J
Operator
Ted Mollring
Onboard fatalities
Unknown
Route
From Jackson, WYTo Scottsdale, AZ
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
Approach · VFR pattern final
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
Undershoot
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
Stall/mush; Wire, static
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 › Go-around, delayed
  • Pilot in command › Stall/mush, inadvertent

Approximate · Estimated position: the centre of Boulder, CO, the place the record names. Not the accident site.

NTSB narrative

THE PILOT REPORTED THAT DURING A NORMAL APPROACH, HE ENCOUNTERED A SEVERE DOWNDRAFT IN WINDS GUSTING ABOUT 40 TO 60 KNOTS. HE STARTED TO ABORT THE LANDING BY RAISING THE GEAR AND APPLYING FULL POWER. THE PILOT STATED THAT HE TURNED RIGHT TO AVOID A HILL, BUT WAS UNABLE TO GAIN ENOUGH ALTITUDE TO CLEAR A HOUSE. THEREFORE, HE CHOPPED THE POWER AND LET THE AIRCRAFT DOWN INTO AN OPEN AREA. A WITNESS STATED THAT THE PLANE APPEARED TO ENTER AN AREA OF SINK THAT IS NORMALLY PRESENT ON THE APPROACH END OF THAT RUNWAY IN HIGH WESTERLY WINDS. THE PASSENGER STATED THAT THE RIGHT WING CLIPPED A POWERLINE BEFORE THE PLANE WENT DOWN AT A SHALLOW ANGLE. THE AIRCRAFT CRASHED ON A GRAVEL ROAD ABOUT 1000 FT FROM THE APPROACH END OF THE RUNWAY. THE ELEVATION WAS ABOUT 5300 FT MSL.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN82DA042
Event ID
20020917X01933
Case number
DEN82DA042
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: 4b1a6b350faae9a3964a602f0774f71a807a3ad795ac05cda0eaef7a1ae83aaf; retrieved 2026-09-24T03:34:10.660Z.