FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95FA112 · Piper PA-32R-300

9 Feb 1995 · Conroe, TX, United States

Piper PA-32R-300 · Accident: in flight collision with terrain/water on approach

From M. Graham Clark Downtown Airport (PLK) to Conroe-North Houston Regional Airport (CXO)

Report a problem

Event

NTSB case
FTW95FA112
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
5 · 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

Piper PA-32R-300

Aircraft type
Piper PA-32
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
N5373F
Operator
Unknown
Onboard fatalities
Unknown
Route
From M. Graham Clark Downtown Airport (PLK), POINT LOOKOUT, MOTo Conroe-North Houston Regional Airport (CXO)
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
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 › IFR procedure, improper

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

NTSB narrative

THE FLIGHT HAD BEEN CLEARED FOR AN ILS RWY 14 APPROACH. WEATHER CONDITIONS PROVIDED TO THE PILOT WAS 100 FEET OBSCURED, VISIBILITY 1/2 MILE IN FOG. THE FLIGHT CALLED THE FBO FOR FIELD CONDITIONS, AND ABOUT 15-20 MINUTES LATER THE AIRPLANE CAME OVER THE FIELD AND MADE A TURN TO THE RIGHT. THE WRECKAGE WAS LOCATED APPROX 1/2 MILE SHORT, AND 1/4 MILE LEFT, OF THE EXTENDED CENTERLINE OF RWY 14. WITNESSES IN THE FBO OFFICE STATED THEY DID NOT HEAR ANY 'CLICKS' OVER THE RADIO NORMALLY HEARD WHEN A PILOT ACTIVATES THE APPROACH LIGHTING SYSTEM. THE PILOT WAS IN THE RIGHT SEAT. THIS WAS THE PILOT'S FIRST FLIGHT INTO THE AIRPORT.

Probable cause

THE PILOT'S FAILURE TO FOLLOW PUBLISHED IFR PROCEDURES. FACTORS WERE THE WEATHER CONDITIONS, THE DARK NIGHT, AND THE PILOT'S FAILURE TO ACTIVATE THE APPROACH LIGHTING SYSTEM.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW95FA112
Event ID
20001207X02953
Case number
FTW95FA112
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 1995-02-10.
  • API snapshot SHA-256: 135bc8748cfb73bad566ef8993674597fe49d5f91c40d082a8ab50af7594e080; retrieved 2026-09-20T23:52:15.835Z.