FTW98LA022 · Cessna 150G
Cessna 150G and Piper PA-60 · Accident: midair collision en route
Event
- NTSB case
- FTW98LA022
- 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
Aircraft 1 · Cessna 150G
- 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
- N3916J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tyler Pounds Regional Airport (TYR)To OKC Will Rogers World Airport (OKC), Oklahoma City, OK
- 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 · climb to 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
- Minor
Aircraft 2 · Piper PA-60
- Aircraft type
- Piper PA-60
- 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
- N602RJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From DTN · Denton, TXTo Tyler Pounds Regional Airport (TYR)
- 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
- 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
Cause areas
- Pilot in command › Became lost/disoriented
- Pilot in command › Procedures/directives, not followed
- Pilot of other aircraft › Became lost/disoriented
- Pilot of other aircraft › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The Piper was inbound for landing and the Cessna was departing the airport and climbing when the two airplanes collided The collision occurred in class D airspace during daylight hours with the visibility reported as 15 miles. The non-federal control tower was manned by one controller who was handling 3 aircraft at the time of the accident. After taking off from runway 22, the Cessna was cleared to depart on a westerly heading. The Cessna pilot intended to drift northeast and intercept highway 64 to follow it to the west. The Cessna pilot missed the highway and drifted too far to the northeast into the final approach course for runway 13. The pilot of the Piper descended his airplane after observing the climbing Cessna at his 2 o'clock position on a collision course. The Cessna pilot pitched his airplane up to avoid the descending Piper. The collision occurred at 1,400 feet MSL, approximately 2 miles northwest of the runway 13. Following the collision, both airplanes landed at the Tyler Airport without further incident. Examination of the airplanes revealed that the top half of the rudder and the vertical stabilizer sustained structural damage on the Piper. Additionally, a section of de-icing boot on the vertical stabilizer was also damaged. The pitot tube, which is installed atop the vertical stabilizer, was knocked off resulting in the loss of airspeed indication in the cockpit. Damage to the Cessna was limited to the nose wheel and tire. According to the Airman's Information Manual, the normal departure procedures is to climb straight ahead to pattern altitude (1,350 feet MSL). If departing the pattern, the airplane should either continue straight out or exit with a 45-degree left turn beyond the departure end of the runway after reaching pattern altitude.
Probable cause
The failure of the pilot of the departing Cessna to follow standard departure procedures and his disorientation while navigating to locate a highway. A factor was the failure by both pilots to maintain visual lookout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA022
- Event ID
- 20001208X09016
- Case number
- FTW98LA022
- 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: 01ea9cad09aa1017d6632b7707250f0a583bc589974c9e0b7155aa8b6b683873; retrieved 2026-09-22T18:17:43.475Z.