![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1287314 |
| Time | |
| Date | 201508 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | CPS.Tower |
| State Reference | IL |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Cessna 402/402C/B379 Businessliner/Utiliner |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Initial Approach |
| Route In Use | VFR Route |
| Flight Plan | VFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (mon) 0.1 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft X; a VFR inbound from the southwest; checked on the frequency upon transfer from ARTCC. Upon initial contact; I told aircraft X that he was cleared into the class B airspace; and to expect runway xx; which was noted closed on the ace-ids. I then believed that I forced the data block on to the arrival scope in order to initiate a point out with the arrival controller. Having a few other aircraft that I was working; my attention was pulled away from completing the manual point out while attending to a number of other aircraft. Aircraft X reported the airport in sight; at which time I had him change frequency to tower in order for them to sequence him into their arrival sequence. They turned aircraft X on to a downwind heading and had him contact the arrival controller in order to be sequenced into the flow for runway yy.the main issue I am aware of in this situation is that I completely forgot that runway xx was closed; even though it was listed as such on the ace-ids and was briefed to me by the controller being relieved at the start of the shift. I should have ensured a manual point out with the arrival controller; since the aircraft would be entering his airspace; at which time he may have informed me that runway xx was closed and would offer a different solution.
Original NASA ASRS Text
Title: TRACON Controller assigned a closed Runway for landing to a VFR aircraft. Tower Controller corrected the instructions and coordinated with the TRACON.
Narrative: Aircraft X; a VFR inbound from the southwest; checked on the frequency upon transfer from ARTCC. Upon initial contact; I told Aircraft X that he was cleared into the Class B airspace; and to expect Runway XX; which was noted closed on the ACE-IDS. I then believed that I forced the data block on to the arrival scope in order to initiate a point out with the arrival controller. Having a few other aircraft that I was working; my attention was pulled away from completing the manual point out while attending to a number of other aircraft. Aircraft X reported the airport in sight; at which time I had him change frequency to Tower in order for them to sequence him into their arrival sequence. They turned Aircraft X on to a downwind heading and had him contact the arrival controller in order to be sequenced into the flow for Runway YY.The main issue I am aware of in this situation is that I completely forgot that Runway XX was closed; even though it was listed as such on the ACE-IDS and was briefed to me by the controller being relieved at the start of the shift. I should have ensured a manual point out with the arrival controller; since the aircraft would be entering his airspace; at which time he may have informed me that Runway XX was closed and would offer a different solution.
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.