37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1365077 |
Time | |
Date | 201606 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | GFK.Tower |
State Reference | ND |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | VFR Route |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | VFR Route |
Flight Plan | VFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.25 |
Person 2 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.5 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
I was controller in charge (controller in charge). Split local controls. Local south was transitioning aircraft X from north to join local north's traffic pattern. Aircraft X was told to follow airport road northbound maintaining 2100 feet or above. Aircraft X was 1 mile west of airport road; local south was aware of it; but gave aircraft X a frequency change to local north anyway. Local south then cleared aircraft Y for takeoff on runway 27L climbing to 3000 feet. Local south then advised local north to turn aircraft X northeast; but by this time; aircraft X had descended to approximately 1800 feet. Aircraft Y continued to climb. Aircraft X then took evasive maneuvers with a sharp turn to the northwest to avoid being hit by aircraft Y. Local south was responsible for aircraft X; even after the frequency change since aircraft X was in his airspace. Local south should have never cleared aircraft Y for takeoff. Local south also coordinated with local north that 58 would be airport road northbound. Local south did not correct the pilot or coordinate differently when aircraft X was off course. We simply got lucky that local north did not have a departure at the same time or there would have been a second near midair. Local north did have departure end at pattern altitude; had he not climbed aircraft X back to 2100 feet after the near midair with aircraft Y; there would have also been a second near midair with [another aircraft]. After the incident; as controller in charge; I started a mor (incident report). At the time of the incident; my supervisor was working ground control and admitted she did not see any of it. She was relieved from ground control and was attempting to force me to change the mor. I refused and made her relieve me from my position. She then attempted to make the mor disappear and sweep it under the rug (similar to the last 3 near midairs at this facility).in my opinion; the pilot of aircraft X made a mistake by descending; however; this incident was caused by local south's poor decision to clear aircraft Y for takeoff; as well as poor coordination and a lack of positive control over aircraft X. This is not a system/airspace/procedure issue. This is an issue of poor decisions and lack of positive control.
Original NASA ASRS Text
Title: A VFR pilot did not comply with Local Control's instructions in the pattern. The pilot in the pattern flew into the path of a departure causing a NMAC.
Narrative: I was Controller In Charge (CIC). Split local controls. Local south was transitioning Aircraft X from north to join local north's traffic pattern. Aircraft X was told to follow airport road northbound maintaining 2100 feet or above. Aircraft X was 1 mile west of airport road; local south was aware of it; but gave Aircraft X a frequency change to local north anyway. Local south then cleared Aircraft Y for takeoff on Runway 27L climbing to 3000 feet. Local south then advised local north to turn Aircraft X northeast; but by this time; Aircraft X had descended to approximately 1800 feet. Aircraft Y continued to climb. Aircraft X then took evasive maneuvers with a sharp turn to the northwest to avoid being hit by Aircraft Y. Local south was responsible for Aircraft X; even after the frequency change since Aircraft X was in his airspace. Local south should have never cleared Aircraft Y for takeoff. Local south also coordinated with local north that 58 would be airport road northbound. Local south did not correct the pilot or coordinate differently when Aircraft X was off course. We simply got lucky that local north did not have a departure at the same time or there would have been a second near midair. Local north did have departure end at pattern altitude; had he not climbed Aircraft X back to 2100 feet after the near midair with Aircraft Y; there would have also been a second near midair with [another aircraft]. After the incident; as CIC; I started a MOR (Incident Report). At the time of the incident; my Supervisor was working Ground Control and admitted she did not see any of it. She was relieved from Ground Control and was attempting to force me to change the MOR. I refused and made her relieve me from my position. She then attempted to make the MOR disappear and sweep it under the rug (similar to the last 3 near midairs at this facility).In my opinion; the pilot of Aircraft X made a mistake by descending; however; this incident was caused by local south's poor decision to clear Aircraft Y for takeoff; as well as poor coordination and a lack of positive control over Aircraft X. This is not a system/airspace/procedure issue. This is an issue of poor decisions and lack of positive control.
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.