 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Juneau tower controller and departing pilot reported confusion on who was to depart resulting in what the pilot reported as a near midair collision.
| Attributes | |
| ACN | 1461703 |
| Time | |
| Date | 201707 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | JNU.Airport |
| State Reference | AK |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Beaver DHC-2 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Route In Use | None |
| Aircraft 2 | |
| Make Model Name | Cessna Aircraft Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Person 2 | |
| Function | Single Pilot Pilot Flying |
| Qualification | Flight Crew Private Flight Crew Sea |
| Experience | Flight Crew Last 90 Days 8 Flight Crew Total 1160 Flight Crew Type 1000 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
Now; there was no loss of separation; but there were a handful of things that happened that were kind of bad. So; aircraft Y called up; ready to go. I scanned the lane and cleared them for takeoff. Seconds after this; aircraft X called up; stated they were west of the aircraft taking off and needed to cross. Now; when I scanned; I only saw one aircraft moving on the pond; aircraft Z; so when I saw aircraft X in relation to this aircraft; it was cool and crossing was no big deal. I crossed aircraft X and noted that aircraft Y was taking an awful long time to start takeoff roll. A second or two later; something caught my eye to the west and I saw aircraft Z in the water lane. I; quickly as I could; instructed aircraft X to hold short and kept him from entering the water lane. Aircraft Y then departed without incident.when aircraft X departed I told them to let me (the controller) determine who they were west and east; they said they hadn't seen aircraft Z behind them.it all worked out; but it could have been way worse.better scans; I figured out that aircraft Z; I hadn't seen was behind one of the window beams.
Original NASA ASRS Text
Title: Juneau Tower Controller and departing pilot reported confusion on who was to depart resulting in what the pilot reported as a NMAC.
Narrative: Now; there was no loss of separation; but there were a handful of things that happened that were kind of bad. So; Aircraft Y called up; ready to go. I scanned the lane and cleared them for takeoff. Seconds after this; Aircraft X called up; stated they were west of the aircraft taking off and needed to cross. Now; when I scanned; I only saw one aircraft moving on the pond; Aircraft Z; so when I saw Aircraft X in relation to this aircraft; it was cool and crossing was no big deal. I crossed Aircraft X and noted that Aircraft Y was taking an awful long time to start takeoff roll. A second or two later; something caught my eye to the west and I saw Aircraft Z in the water lane. I; quickly as I could; instructed Aircraft X to hold short and kept him from entering the water lane. Aircraft Y then departed without incident.When Aircraft X departed I told them to let me (the controller) determine who they were west and east; they said they hadn't seen Aircraft Z behind them.It all worked out; but it could have been way worse.Better scans; I figured out that Aircraft Z; I hadn't seen was behind one of the window beams.
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.