FTW95FA087 · Beech B95
Beech B95 · Accident: in flight collision with object on approach
From Natchez–Adams County Airport / Hardy-Anders Field (HEZ) to Memorial Field Airport (HOT)
Event
- NTSB case
- FTW95FA087
- 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
- 3 · 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 B95
- Aircraft type
- Beechcraft 95
- 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
- N673Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Natchez–Adams County Airport / Hardy-Anders Field (HEZ), Natchez, MSTo Memorial Field Airport (HOT)
- 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 · IFR missed 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 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
- Tower (marked)
- 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 › IFR procedure, not followed
- Pilot in command › Missed approach, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DUE TO ATC WORKLOAD, THE CONTROLLER COULD NOT PROVIDE VECTORS FOR THE ILS RUNWAY 5. AFTER BEING FLOWN THROUGH THE FINAL APPROACH COURSE ATC CLEARED N673Q FOR THE ILS AND TO PROCEED DIRECT TO THE OUTER MARKER (HOSSY). THIS REQUIRED AN APPROXIMATE 180 DEGREE RIGHT TURN. N673Q WAS ALSO INSTRUCTED TO MAINTAIN 3,500 FEET UNTIL HOSSY; GLIDESLOPE INTERCEPT ALTITUDE AT HOSSY WAS 2,300 FEET. THE PILOT TURNED ABOUT 90 DEGREES INBOUND (LEFT) AT HOSSY RATHER THAN EXECUTING A PROCEDURE TURN. ACCORDING TO RECORDED RADAR DATA, THE AIRPLANE'S FLIGHT PATH FROM HOSSY TO THE MISSED APPROACH POINT WAS SOUTH (RIGHT) OF THE INBOUND COURSE. ADDITIONALLY, THE RADAR DATA SHOWS THE AIRPLANE PROCEEDING NORTHBOUND BEYOND THE TERMINAL VOR. THE MISSED APPROACH PROCEDURE FOR THE ILS RUNWAY 5 APPROACH IS A CLIMBING RIGHT TURN TO 3000 FEET. THE RIGHT TURN PROVIDES CLEARANCE FROM A MOUNTAIN WITH TOWERS NORTH OF THE AIRPORT. A 3.5 FOOT SECTION OF THE RIGHT WING WAS RECOVERED 5 FEET FROM THE TOP OF A 200 FOOT TOWER APPROXIMATELY 1.5 NAUTICAL MILES NORTH-NORTHEAST OF THE RUNWAY.
Probable cause
THE PILOT'S FAILURE TO FOLLOW IFR AND MISSED APPROACH PROCEDURES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95FA087
- Event ID
- 20001207X02850
- Case number
- FTW95FA087
- 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: e98527e79ac4445cd6d812a0c6ced8fbf8e7b30fd17b46b5844c5c96afc8629b; retrieved 2026-09-20T23:53:27.634Z.