37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1317426 |
Time | |
Date | 201512 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | GFK.TRACON |
State Reference | ND |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | None |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Person 1 | |
Function | Instructor Pilot Flying |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 79 Flight Crew Total 312 Flight Crew Type 38 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 300 Vertical 200 |
Narrative:
We were flying inbound to east ponds (VFR reporting point for aircraft) nearing the end of our descent and we were in contact with gfk approach. Approach instructed [another aircraft] to 'execute a right 360 for sequencing.' approach had to repeat that instruction before [the other aircraft] responded. Approach then told us; 'traffic is 11 o'clock; 1 mile; southwest bound; 2;200 feet; traffic will be doing a right 360 to get behind you.' I responded that we had the traffic in sight. I also adjusted our heading to the right (more west bound; instead of southwest bound) to increase spacing from [the other aircraft]. Approach then told [the other aircraft]; 'traffic northeast of your position; 1 mile; southwest bound; 2;800; has you in sight; you'll be following them into east ponds.' [the other aircraft] responded that they were looking for traffic. I looked back up from setting the new heading; and couldn't find [the other aircraft] outside. I asked the PNF if he still had the traffic in sight and he wasn't aware that we had even been issued traffic advisories. At that point; I glanced at the ads-B and saw [the other aircraft] disappear. I went back to scanning for traffic outside; and then noticed [the other aircraft] re-appear from behind our left wing still in the right 360. They were approximately 300 feet from us horizontally and about 200 feet below us. I immediately disconnected the autopilot and initiated a climb and banked away from [the other aircraft]. Approach did not issue another traffic advisory until [the other aircraft] had completed their 360 turn; then they were told; 'traffic is west of your position; 2 miles; southwest bound; 2;100; follow them into east ponds.' [the other aircraft] reported us in sight; and then approach had us contact tower. We completed the remainder of the flight without incident.as for corrective actions; listen to ATC's instructions for other aircraft; and speak-up if something doesn't sound right. Gfk approach should have instructed the traffic to make a left 360; rather than a right 360. Also; make sure the PNF is maintaining visual contact with the traffic or is at least scanning for the traffic.
Original NASA ASRS Text
Title: Pilot reported an NMAC with another light aircraft during arrival into GFK airport.
Narrative: We were flying inbound to East Ponds (VFR reporting point for aircraft) nearing the end of our descent and we were in contact with GFK Approach. Approach instructed [another aircraft] to 'execute a right 360 for sequencing.' Approach had to repeat that instruction before [the other aircraft] responded. Approach then told us; 'Traffic is 11 o'clock; 1 mile; southwest bound; 2;200 feet; traffic will be doing a right 360 to get behind you.' I responded that we had the traffic in sight. I also adjusted our heading to the right (more west bound; instead of southwest bound) to increase spacing from [the other aircraft]. Approach then told [the other aircraft]; 'Traffic northeast of your position; 1 mile; southwest bound; 2;800; has you in sight; you'll be following them into East Ponds.' [The other aircraft] responded that they were looking for traffic. I looked back up from setting the new heading; and couldn't find [the other aircraft] outside. I asked the PNF if he still had the traffic in sight and he wasn't aware that we had even been issued traffic advisories. At that point; I glanced at the ADS-B and saw [the other aircraft] disappear. I went back to scanning for traffic outside; and then noticed [the other aircraft] re-appear from behind our left wing still in the right 360. They were approximately 300 feet from us horizontally and about 200 feet below us. I immediately disconnected the autopilot and initiated a climb and banked away from [the other aircraft]. Approach did not issue another traffic advisory until [the other aircraft] had completed their 360 turn; then they were told; 'Traffic is west of your position; 2 miles; southwest bound; 2;100; follow them into East Ponds.' [The other aircraft] reported us in sight; and then Approach had us contact Tower. We completed the remainder of the flight without incident.As for corrective actions; listen to ATC's instructions for other aircraft; and speak-up if something doesn't sound right. GFK Approach should have instructed the traffic to make a left 360; rather than a right 360. Also; make sure the PNF is maintaining visual contact with the traffic or is at least scanning for the traffic.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.