FTW01FA025 · Cessna 172N
Cessna 172N and Cessna 150E · Accident: midair collision en route
Event
- NTSB case
- FTW01FA025
- 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
- Visual Meteorological Cond
Aircraft 1 · Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N6521D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Antonio International Airport (SAT), San Antonio, TXTo 3R1 · Baytown, TX
- 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
- En route · cruise
- 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Cessna 150E
- Aircraft type
- Cessna 150
- 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
- N3588J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Easterwood Field (CLL), College Station, TXTo Reed Airport (5TA4), Houston, TX
- 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
- En route · cruise
- 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
- Midair collision
- 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 › Visual lookout, not maintained
- Pilot of other aircraft › Visual lookout, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Cessna 172 was flying level at 2,000 feet, eastbound, when the pilot noticed the Cessna 150 approaching from her left side at a 90-degree angle (from the north). She reported that the Cessna 150 was at an altitude slightly below her airplane's altitude. She entered a climbing right turn and, subsequently, the airplanes collided. The Cessna 172's right main landing gear separated and its right wing and aileron were structurally damaged. The Cessna 172 was able to sustain flight and landed at an airport located approximately 10 miles from the collision area. The Cessna 150 entered an uncontrolled descent and impacted the ground. Two witnesses reported sun glare from the west at the time of the accident. One pilot witness, who departed near the same time as the Cessna 150, and flew the same route as the Cessna 150, stated that the sun was "blinding from [his] 2:00 o'clock to 4:00 o'clock position." He added that the visibility to the south and east was 15 miles or greater and the sky was clear of clouds. Another pilot witness, who departed from the airport the Cessna 172 landed at about 10 minutes before the accident, and was traveling on a northwesterly heading, reported that he observed a "very strong sun glare" and it "seemed impossible to see within plus or minus 15 degrees from the sun's bearing." The witness added that a cold front had passed through the area the day before the accident, and the sky was clear of clouds and haze.
Probable cause
the failure of both pilots to maintain visual lookout during cruise flight. A contributory factor was sun glare, which obscured the Cessna 150 pilot's visual lookout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01FA025
- Event ID
- 20001212X22287
- Case number
- FTW01FA025
- 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: bb35bdaeca64bb6a596eee9a7ba34bd391a5ba9a2939b460d0c49b1442b6722b; retrieved 2026-09-20T20:45:25.533Z.