37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 277496 |
Time | |
Date | 199407 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ewr |
State Reference | NJ |
Altitude | msl bound lower : 2000 msl bound upper : 2000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : n90 tower : ewr tower : tmb |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | descent : approach descent other |
Route In Use | arrival other |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Airbus Industrie Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 250 flight time total : 4800 flight time type : 250 |
ASRS Report | 277496 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 228 flight time total : 5000 flight time type : 2700 |
ASRS Report | 278042 |
Events | |
Anomaly | conflict : airborne less severe other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | faa : reviewed incident with flight crew Other |
Miss Distance | horizontal : 12000 vertical : 750 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error Inter Facility Coordination Failure |
Narrative:
Flight was en route from phl to ewr. Ewr was landing and departing on runways 22R&left. The winds at ewr were 350 degrees at 10 KTS. We were told to expect the ILS runway 22L but then tower decided to switch around to the 4's, so approach told us to expect the ILS runway 4R. Approach control (128.55) gave us vectors for the approach and everything was going normal. The captain and I set up for the approach and went through the checklist. Approach gave us an intercept heading and the localizer was coming in as expected. Approach cleared us for the ILS runway 4R and switched us over to tower frequency about 9 mi south of the field. I checked in with tower and he seemed very confused on who we were and asked us to identify for him. We complied with his request and he then immediately and frantically gave us a 090 degree heading off the localizer and told us to descend to 1500 ft (from 2000 ft). He also told us he had a dc-10 at 2000 ft and 2 mi. The captain put the aircraft into the turn while pulling off the power to start his descent. (This maneuver set off the GPWS altitude and bank angle warnings.) about 15- 20 seconds later, the tower told us that the dc-10 (later we found out it was an airbus) had passed behind us and now was at 2500 ft. Tower gave us a vector and told us to climb to 3000 ft then told us to execute the published missed approach procedure. When we checked in with approach control again (119.2) he, too, seemed a little confused on who we were (air carrier ax). He asked us to identify for him and then he started calling us air carrier ab, and told us to climb to 5000 ft on a 030 degree heading. The captain and I were skeptical so I asked to clarify air carrier ax squawk code as our own. He came back saying 'I don't care what your squawk is!' and then repeated air carrier ab climb and maintain 5000 ft on a 030 degree heading. Question: who are we? Air carrier ax as filed or air carrier ab? We took the call and started up to 5000 ft and turned to the heading. We were vectored around for another ILS, the whole time being called air carrier ab. We landed without further incident. I believe a failure in communication between approach control and tower occurred on arrival and also on missed approach. Why were we cleared the ILS runway 4R when tower was still sending off aircraft north runways 22R&left? And why was our flight number changed on missed approach? The only answer I have is a lack of communication between tower and approach control. Supplemental information from acn 278042: after climbing to 5000 ft I asked for a phone number to call when we got on the ground! After talking to new york approach on the phone and tower (ewr) supervisor on the phone, I called our director of operations to make them aware of the near midair. The next day I called ewr tower and filed a near miss report. As of now, we are waiting to hear the investigating reports.
Original NASA ASRS Text
Title: LTT INSTRUCTED TO MAKE MISSED APCH DUE TO PROX OF ANOTHER ACFT DURING RWY CHANGE. APCH USED WRONG CALL SIGN DURING ENSUING INSTRUCTIONS.
Narrative: FLT WAS ENRTE FROM PHL TO EWR. EWR WAS LNDG AND DEPARTING ON RWYS 22R&L. THE WINDS AT EWR WERE 350 DEGS AT 10 KTS. WE WERE TOLD TO EXPECT THE ILS RWY 22L BUT THEN TWR DECIDED TO SWITCH AROUND TO THE 4'S, SO APCH TOLD US TO EXPECT THE ILS RWY 4R. APCH CTL (128.55) GAVE US VECTORS FOR THE APCH AND EVERYTHING WAS GOING NORMAL. THE CAPT AND I SET UP FOR THE APCH AND WENT THROUGH THE CHKLIST. APCH GAVE US AN INTERCEPT HDG AND THE LOC WAS COMING IN AS EXPECTED. APCH CLRED US FOR THE ILS RWY 4R AND SWITCHED US OVER TO TWR FREQ ABOUT 9 MI S OF THE FIELD. I CHKED IN WITH TWR AND HE SEEMED VERY CONFUSED ON WHO WE WERE AND ASKED US TO IDENT FOR HIM. WE COMPLIED WITH HIS REQUEST AND HE THEN IMMEDIATELY AND FRANTICALLY GAVE US A 090 DEG HDG OFF THE LOC AND TOLD US TO DSND TO 1500 FT (FROM 2000 FT). HE ALSO TOLD US HE HAD A DC-10 AT 2000 FT AND 2 MI. THE CAPT PUT THE ACFT INTO THE TURN WHILE PULLING OFF THE PWR TO START HIS DSCNT. (THIS MANEUVER SET OFF THE GPWS ALT AND BANK ANGLE WARNINGS.) ABOUT 15- 20 SECONDS LATER, THE TWR TOLD US THAT THE DC-10 (LATER WE FOUND OUT IT WAS AN AIRBUS) HAD PASSED BEHIND US AND NOW WAS AT 2500 FT. TWR GAVE US A VECTOR AND TOLD US TO CLB TO 3000 FT THEN TOLD US TO EXECUTE THE PUBLISHED MISSED APCH PROC. WHEN WE CHKED IN WITH APCH CTL AGAIN (119.2) HE, TOO, SEEMED A LITTLE CONFUSED ON WHO WE WERE (ACR AX). HE ASKED US TO IDENT FOR HIM AND THEN HE STARTED CALLING US ACR AB, AND TOLD US TO CLB TO 5000 FT ON A 030 DEG HDG. THE CAPT AND I WERE SKEPTICAL SO I ASKED TO CLARIFY ACR AX SQUAWK CODE AS OUR OWN. HE CAME BACK SAYING 'I DON'T CARE WHAT YOUR SQUAWK IS!' AND THEN REPEATED ACR AB CLB AND MAINTAIN 5000 FT ON A 030 DEG HDG. QUESTION: WHO ARE WE? ACR AX AS FILED OR ACR AB? WE TOOK THE CALL AND STARTED UP TO 5000 FT AND TURNED TO THE HDG. WE WERE VECTORED AROUND FOR ANOTHER ILS, THE WHOLE TIME BEING CALLED ACR AB. WE LANDED WITHOUT FURTHER INCIDENT. I BELIEVE A FAILURE IN COM BTWN APCH CTL AND TWR OCCURRED ON ARR AND ALSO ON MISSED APCH. WHY WERE WE CLRED THE ILS RWY 4R WHEN TWR WAS STILL SENDING OFF ACFT N RWYS 22R&L? AND WHY WAS OUR FLT NUMBER CHANGED ON MISSED APCH? THE ONLY ANSWER I HAVE IS A LACK OF COM BTWN TWR AND APCH CTL. SUPPLEMENTAL INFO FROM ACN 278042: AFTER CLBING TO 5000 FT I ASKED FOR A PHONE NUMBER TO CALL WHEN WE GOT ON THE GND! AFTER TALKING TO NEW YORK APCH ON THE PHONE AND TWR (EWR) SUPVR ON THE PHONE, I CALLED OUR DIRECTOR OF OPS TO MAKE THEM AWARE OF THE NEAR MIDAIR. THE NEXT DAY I CALLED EWR TWR AND FILED A NEAR MISS RPT. AS OF NOW, WE ARE WAITING TO HEAR THE INVESTIGATING RPTS.
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.