No fatalities

29 Jan 2019: Cessna 172 S (N565SP) — Skymates Inc. — Grand Prairie, TX

Grand Prairie, TX, United States

On 29 Jan 2019, a Cessna 172 S (registration N565SP) operated by Skymates Inc. was involved in an aviation accident near Grand Prairie, TX. No fatalities were reported. Investigators recorded the probable cause as: The failure of the pilots of both airplanes to see and avoid the other airplane while entering the airport traffic pattern in visual meteorological conditions. This summary draws on records from NTSB; 13 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

Two Cessna 172S aircraft collided in midair about 6 miles south of Grand Prairie Municipal Airport, Texas, on January 29, 2019. Both aircraft sustained substantial damage; no injuries occurred to the four occupants.

History of Flight

On January 29, 2019, at 1329 central standard time, two Cessna 172S aircraft, N565SP and N52243, collided in midair approximately 6 miles south of Grand Prairie Municipal Airport (GPM) in Grand Prairie, Texas. Both airplanes were operated by Skymates Flight Academy under Title 14 Code of Federal Regulations Part 91 as instructional flights. N565SP was registered to LLP Leasing Group, LLC, and N52243 to Skymates, Inc. Day visual meteorological conditions prevailed, and neither flight was operating on a flight plan. Both local flights originated from GPM around 1230.

At 1327:54, the pilot of N565SP contacted the GPM control tower, reporting their position near the southern tip of Joe Pool Lake, about 10 miles south of the airport. At 1328:39, the pilot of N52243 reported 7 miles south of the airport. The tower controller instructed both pilots to enter a left downwind for landing on runway 17. Radar data indicated that N565SP was approximately 0.1 mile west of N52243 at that time, with N565SP at about 2,300 ft mean sea level (msl) and N52243 at about 2,400 ft msl. The flight paths converged near the south tip of Joe Pool Lake. At about 1328:39, the radar tracks merged and remained in close proximity for approximately 58 seconds (1.6 miles) before diverging abruptly.

At 1329:05, the pilot of N565SP requested clarification of the assigned transponder code. During the transmission, an audible conflict alert was heard in the control tower cab. At that time, radar data indicated N565SP at 2,500 ft and N52243 at 2,400 ft.

At 1329:28, the tower controller instructed N52243 to start a turn toward the northeast corner of the lake. At 1329:37, the pilot of N52243 declared an emergency; the nature of the emergency was unintelligible in the initial transmission. The controller acknowledged and inquired about the nature of the emergency. At 1329:51, the pilot of N565SP transmitted “just had an airplane hit us from the back.” The controller again queried N52243 for the nature of the emergency, and the pilot replied, “still good” and that they would report downwind for runway 17. A few seconds later, the pilot of N565SP requested the controller to check the landing gear as the airplane approached the airport. The controller cleared the pilot for a straight-in approach to runway 35.

At 1330:51, the controller instructed the pilot of N52243 to execute a left 360° turn, at which time the pilot informed the controller of damage to the right wing and cowling and requested a straight-in approach. The controller transmitted “understand you are declaring an emergency” and cleared the flight to land on runway 35, “number one.” The controller then instructed the pilot of N565SP to execute a right 360° turn for spacing, followed by a straight-in approach to runway 35. The controller asked if there had been a midair collision, and the pilot of N565SP confirmed. Both airplanes subsequently landed without further incident.

The flight instructor of N565SP reported that after contacting the GPM tower controller at the south tip of Joe Pool Lake, he noticed another airplane in his peripheral vision approaching from the left and behind but did not have time to react to avoid the collision. He maintained control and landed at GPM.

The flight instructor of N52243 reported that he saw an airplane “suddenly appeared in front” of them at 2,500 ft msl. He estimated the impact occurred within one second of observing the airplane. He immediately reduced engine power, entered a descending left turn, maintained control, and continued to GPM, landing without further damage.

Meteorological Information

At 1250 and 1350, the GPM Automated Weather Observing System recorded clear skies and 10 miles visibility with no obscuration.

Wreckage and Impact Information

N565SP sustained damage to the left wing, flap, and aileron. The outboard wing leading edge was dented, and the lower wing skin was buckled forward of the flap. A cut in the lower wing skin was located immediately forward of the aileron. The aileron was buckled and deformed over approximately one-half the span. The aileron mounting hinge and control system continuity were intact. The left wing flap trailing edge was dented near mid-span.

N52243 sustained damage to the right wing, engine cowling, and windshield. The right wing leading edge was deformed, and the wing skin was torn about one-third span from the wing root. The wing leading edge was damaged over an approximately 18-inch width by 6-inch deep area. The wing spar appeared intact. The upper right side of the engine cowling was dented and creased. The right side of the windshield exhibited scrape and scuffing marks.

Additional Information

Federal Aviation Regulations (14 CFR §91.113) require that when weather conditions permit, vigilance shall be maintained to see and avoid other aircraft. Regarding right-of-way, when aircraft of the same category are converging at approximately the same altitude, the aircraft to the other’s right has the right-of-way. An aircraft being overtaken has the right-of-way, and the overtaking aircraft shall alter course to the right to pass well clear. For aircraft approaching an airport for landing, the aircraft at lower altitude has the right-of-way, but shall not cut in front of another on final approach.

FAA Order 7110.65 prescribes air traffic control procedures, stating that the primary purpose of the ATC system is to prevent collisions and provide a safe, orderly flow of traffic. The order specifies that a controller’s first priority is separating aircraft and issuing safety alerts, including issuing a safety alert if an aircraft is in unsafe proximity to another aircraft.

Contributing factors

Causes

Instructor/check pilotStudent/instructed pilotPilot of other aircraft

Other contributing factors

ATC personnel