DEN84FA121 · Aero Commander 500-B
Aero Commander 500-B · Accident: in flight collision with terrain/water on approach
From Billings Logan International Airport (BIL) to an unrecorded destination
Event
- NTSB case
- DEN84FA121
- 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
- Charter & commuter
- 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
Aero Commander 500-B
- Aircraft type
- Aero Commander 500
- 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
- N743W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Billings Logan International Airport (BIL), Billings, MTTo not recorded
- 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 135: Air Taxi & Commuter
- 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 · IFR final approach
- 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 terrain/water
- 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 › Altimeter setting, improper
- Pilot in command › IFR procedure, improper
- Pilot in command › Minimum descent altitude, not maintained
- Pilot in command › Proper altitude, below
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT SAID THAT WHEN HE CALLED ON THE RADIO PRIOR TO THE APPROACH FOR AN ALTIMETER SETTING THE REPLY WAS '30.11 OR 30.12, SOMETHING LIKE THAT.' THE ACFT ALTIMETER WAS FOUND AFTER THE ACCIDENT SET AT 30.22 INCHES OF MERCURY. THE VISIBILITY WAS DESCRIBED AS 1 AND 1/2 MILES IN SNOW SHOWERS. HE CONTINUED THE APPROACH 'BECAUSE MINIMUMS ARE ONE MILE.' HE DESCENDED OUTBOUND TO 4500 FT. MINIMUM PROCEDURE TURN ALT IS 4700 FT MSL. THE PLT THEN DESCENDED TO 3700 FT MSL AS HEAPPROACHED THE VOR. POWER WAS REDUCED TO 17-18 INCHES OF MANIFOLD PRESSURE AND AIRSPEED REDUCED TO 120 KTS. AS THE VOR WAS CROSSED HE GLANCED AT THE ALTIMETER AND 'THE HANDS WERE IN THE TWO O'CLOCK POSITION.' LANDING GEAR WAS EXTENDED AND APPROACH FLAPS SET. THE PLT SAID ALL SEEMED NORMAL. HE LOOKED OUT THE WINDOW AND SAW 'WISPY CLOUDS GOING BY RAPIDLY. THEN THERE WERE THE SOUNDS OF IMPACT.' THE NEXT THING REMEMBERED WAS THE SOUND OF DRIPPING GASOLINE. THE PLT SAID HE CRAWLED OUT OF THE COCKPIT WINDOW AND WANDERED 'FOR A COUPLE HOURS TRYING TO CHASE DOWN THE SEARCH LIGHTS.'
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN84FA121
- Event ID
- 20001214X39004
- Case number
- DEN84FA121
- 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: 8c76f676d8184b909dd1bd47080f693191d29108309fc29082e1eb6e4f383740; retrieved 2026-09-18T20:42:45.603Z.