DFW07LA022 · Cessna 152
Cessna 152 and Cessna 152 · Accident: midair collision on approach
Event
- NTSB case
- DFW07LA022
- 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
- Unknown
- 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 152
- Aircraft type
- Cessna 152
- 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
- N94684
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monroe Regional Airport (MLU)To Monroe Regional Airport (MLU), Monroe, LA
- 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
Aircraft 2 · Cessna 152
- Aircraft type
- Cessna 152
- 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
- N94553
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monroe Regional Airport (MLU), Monroe, LATo Monroe Regional Airport (MLU), Monroe, LA
- 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
- Minor
Cause areas
- Atc personnel(lcl/gnd/clnc) › Identification of aircraft visually, not performed
- Pilot in command › Visual lookout, inadequate
- Pilot in command › Visual separation, not maintained
- Pilot of other aircraft › Visual lookout, inadequate
- Pilot of other aircraft › Visual separation, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
There were four airplanes in the traffic pattern at the time of the mishap. The airplanes involved in the mishap were in the closed left hand traffic pattern for runway 04. Both pilots were given directions from tower to follow preceding traffic. While established on final, the pilot reported the wrong position number, resulting in the second pilot not aware of three airplanes on final. While maneuvering from downwind leg to final, the second pilot lost situational awareness and did not anticipate the preceding airplane on final, resulting in an in-flight collision. Since the airplane was a high wing airplane, the first pilot was not able to visually clear for the second aircraft rolling base to final. The tower controller did not provide proper separation to either pilot.
Probable cause
The failure of the second pilot to maintain separation from the preceding traffic established on final approach. A contributing factor was the failure by ATC personnel to visually identify and separate airplanes in the traffic pattern.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW07LA022
- Event ID
- 20070227X00233
- Case number
- DFW07LA022
- 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, coordinates. 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: cae38752957ab77e30bee12f5f14b0c44972958083d8ebdda38eb4447b19817d; retrieved 2026-09-22T04:15:13.012Z.