 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Operational deviation air carrier X on approach not switched to tower frequency execute go around while tower released air carrier Y for departure on crossing runway.
| Attributes | |
| ACN | 292433 |
| Time | |
| Date | 199412 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : jax |
| State Reference | FL |
| Environment | |
| Flight Conditions | IMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : jax tower : jax |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach landing : missed approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | B727 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial climbout : takeoff |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| ASRS Report | 292433 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
OJT being provided by myself to a developmental atcs. WX was decreasing, but NWS still reporting VFR. Pilot reports indicate IFR. We are using localizer or localizer back course to stay aligned with 15 KT wind. ILS available, but would be tailwind. B737 was issued approach clearance by the developmental, but never told to contact tower. I did not recognize the lack of the frequency change. 2 mins later, the B737 advised he was 'going around' on approach frequency. Tower never questioned us (approach) as to why the B737 was not on their frequency. At the same time, tower cleared a B727 for takeoff on a crossing runway. Climb out for missed approach and departure crossed paths, but the missed approach aircraft was more than 1000 ft above the departure aircraft when they crossed. Suggestionsecond officerbservations: 1) I should have observed that the change to tower for the arrival had not been done. 2) flight crew of arrival should have noticed same. 3) tower should have noticed same, and not departed another aircraft.
Original NASA ASRS Text
Title: OPDEV ACR X ON APCH NOT SWITCHED TO TWR FREQ EXECUTE GAR WHILE TWR RELEASED ACR Y FOR DEP ON XING RWY.
Narrative: OJT BEING PROVIDED BY MYSELF TO A DEVELOPMENTAL ATCS. WX WAS DECREASING, BUT NWS STILL RPTING VFR. PLT RPTS INDICATE IFR. WE ARE USING LOC OR LOC BACK COURSE TO STAY ALIGNED WITH 15 KT WIND. ILS AVAILABLE, BUT WOULD BE TAILWIND. B737 WAS ISSUED APCH CLRNC BY THE DEVELOPMENTAL, BUT NEVER TOLD TO CONTACT TWR. I DID NOT RECOGNIZE THE LACK OF THE FREQ CHANGE. 2 MINS LATER, THE B737 ADVISED HE WAS 'GOING AROUND' ON APCH FREQ. TWR NEVER QUESTIONED US (APCH) AS TO WHY THE B737 WAS NOT ON THEIR FREQ. AT THE SAME TIME, TWR CLRED A B727 FOR TKOF ON A XING RWY. CLBOUT FOR MISSED APCH AND DEP CROSSED PATHS, BUT THE MISSED APCH ACFT WAS MORE THAN 1000 FT ABOVE THE DEP ACFT WHEN THEY CROSSED. SUGGESTIONS/OBSERVATIONS: 1) I SHOULD HAVE OBSERVED THAT THE CHANGE TO TWR FOR THE ARR HAD NOT BEEN DONE. 2) FLC OF ARR SHOULD HAVE NOTICED SAME. 3) TWR SHOULD HAVE NOTICED SAME, AND NOT DEPARTED ANOTHER ACFT.
Data retrieved from NASA's ASRS site as of July 2007 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.