37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 430094 |
Time | |
Date | 199903 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : col.vor |
State Reference | NJ |
Altitude | msl bound lower : 6000 msl bound upper : 6300 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : n90.tracon |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure sid : newark 6 |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : n90.tracon |
Operator | common carrier : air carrier |
Make Model Name | B727 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach descent : intermediate altitude |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 14000 flight time type : 2200 |
ASRS Report | 430094 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 5000 flight time type : 3000 |
ASRS Report | 430340 |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure other anomaly other other spatial deviation |
Independent Detector | aircraft equipment : tcas other flight crewa |
Resolutory Action | controller : issued advisory flight crew : took evasive action |
Miss Distance | horizontal : 9000 vertical : 300 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Aircraft had leveled off at 6000 ft on the ewr departure out of ewr. Departure control called B727 traffic, at 7000 ft, from right to left in front of aircraft. I then saw another target on the TCASII at 6000 ft (co-altitude) at 2 O'clock, 5 mi and closing. I asked departure if he had this traffic. Before he could respond, the TCASII gave an RA alert along with 'climb' command. The first officer was flying and I directed him to click off the autoplt and commence a slow climb because the B727 traffic was passing in front of us at 7000 ft. We climbed to 6300 ft, leveled off, and spotted the 6000 ft traffic passing our right side at 1 1/2 mi. We told departure we were clear of traffic and descended back to 6000 ft. We passed under the B727 at 7000 ft shortly thereafter. We asked the controller where the co-altitude traffic had come from and he replied it was with approach control and he'd find out what happened. This appears to be a breakdown between departure and approach control. Departure seemed as surprised as we were when the traffic popped up. What really made the situation dangerous was the B727 traffic at 7000 ft on our nose. It was almost like being driven into a box canyon. As a crew, we kept talking to each other and evaluating the situation and our actions to ensure safety. We have had a lot of CRM training the last several yrs and it came in handy. Supplemental information from acn 430340: the purpose for writing this is to detail a possible failure to intercept a radial along flight plan route at a turnpoint resulting in loss of horizontal separation between our aircraft and unknown other(south). The unusual and mitigating circumstances provide the cause for it and may be helpful in preventing future occurrences. Beginning with a seemingly normal takeoff at ewr on runway 22L, we incurred a vertical gyro failure on the right (first officer) side with simultaneous failure of both DME's (or DME transmitter on the field). Takeoff was accomplished by me without any cockpit presentation of pitch or bank aside from looking out the side window and looking to the left side captain's vertical gyro for reference. The SID (ewr 6 departure, white transition) requires 5 turns until proceeding on course. We attempted the first 2 without DME, then switched to first officer alternate gyro. A short time later at 5000 ft or 6000 ft, our TCASII showed a traffic conflict at 3 O'clock, same altitude, coming toward us (eastbound). While we were on course proceeding sbound on or near the colts neck 350 degree radial, the TCASII then gave a 'climb' command. WX was MVFR. I began a slight 200-300 ft climb while observing traffic passing off our right and behind us within 2 mi. The captain (PNF) notified new york departure of our TCASII traffic and informed them we were climbing. ATC acknowledged and apologetically indicated it was their arrival traffic into ewr. They then asked us to return to assigned altitude when able due to passing traffic above, from right to left (west to east) above us 1000 ft. We complied. The cockpit in all this was extremely busy with crew coordination regarding collision avoidance maneuver, multiple cockpit instrument failure earlier, and continuing real time traffic observance in the vicinity. Somewhere and sometime shortly afterwards, we may have overflown a turnpoint at white intersection to intercept the coyle 226 degree course. ATC by now had been switched, we think, to ZNY or ZDC, who was likely unaware of our TCASII conflict and resulting deviation from flight path. This could only be prevented in future by thorough communication between ATC facilities or quicker pilot reaction to course tracking while in the midst (or shortly after) of an emergency maneuver situation. Also, it would help if ATC would call or warn aircraft if they sense a potential conflict.
Original NASA ASRS Text
Title: ACR FLC INITIATE TCASII EVASIVE MANEUVER DUE TO SAME ALT XING TFC IN N90 AIRSPACE.
Narrative: ACFT HAD LEVELED OFF AT 6000 FT ON THE EWR DEP OUT OF EWR. DEP CTL CALLED B727 TFC, AT 7000 FT, FROM R TO L IN FRONT OF ACFT. I THEN SAW ANOTHER TARGET ON THE TCASII AT 6000 FT (CO-ALT) AT 2 O'CLOCK, 5 MI AND CLOSING. I ASKED DEP IF HE HAD THIS TFC. BEFORE HE COULD RESPOND, THE TCASII GAVE AN RA ALERT ALONG WITH 'CLB' COMMAND. THE FO WAS FLYING AND I DIRECTED HIM TO CLICK OFF THE AUTOPLT AND COMMENCE A SLOW CLB BECAUSE THE B727 TFC WAS PASSING IN FRONT OF US AT 7000 FT. WE CLBED TO 6300 FT, LEVELED OFF, AND SPOTTED THE 6000 FT TFC PASSING OUR R SIDE AT 1 1/2 MI. WE TOLD DEP WE WERE CLR OF TFC AND DSNDED BACK TO 6000 FT. WE PASSED UNDER THE B727 AT 7000 FT SHORTLY THEREAFTER. WE ASKED THE CTLR WHERE THE CO-ALT TFC HAD COME FROM AND HE REPLIED IT WAS WITH APCH CTL AND HE'D FIND OUT WHAT HAPPENED. THIS APPEARS TO BE A BREAKDOWN BTWN DEP AND APCH CTL. DEP SEEMED AS SURPRISED AS WE WERE WHEN THE TFC POPPED UP. WHAT REALLY MADE THE SIT DANGEROUS WAS THE B727 TFC AT 7000 FT ON OUR NOSE. IT WAS ALMOST LIKE BEING DRIVEN INTO A BOX CANYON. AS A CREW, WE KEPT TALKING TO EACH OTHER AND EVALUATING THE SIT AND OUR ACTIONS TO ENSURE SAFETY. WE HAVE HAD A LOT OF CRM TRAINING THE LAST SEVERAL YRS AND IT CAME IN HANDY. SUPPLEMENTAL INFO FROM ACN 430340: THE PURPOSE FOR WRITING THIS IS TO DETAIL A POSSIBLE FAILURE TO INTERCEPT A RADIAL ALONG FLT PLAN RTE AT A TURNPOINT RESULTING IN LOSS OF HORIZ SEPARATION BTWN OUR ACFT AND UNKNOWN OTHER(S). THE UNUSUAL AND MITIGATING CIRCUMSTANCES PROVIDE THE CAUSE FOR IT AND MAY BE HELPFUL IN PREVENTING FUTURE OCCURRENCES. BEGINNING WITH A SEEMINGLY NORMAL TKOF AT EWR ON RWY 22L, WE INCURRED A VERT GYRO FAILURE ON THE R (FO) SIDE WITH SIMULTANEOUS FAILURE OF BOTH DME'S (OR DME XMITTER ON THE FIELD). TKOF WAS ACCOMPLISHED BY ME WITHOUT ANY COCKPIT PRESENTATION OF PITCH OR BANK ASIDE FROM LOOKING OUT THE SIDE WINDOW AND LOOKING TO THE L SIDE CAPT'S VERT GYRO FOR REF. THE SID (EWR 6 DEP, WHITE TRANSITION) REQUIRES 5 TURNS UNTIL PROCEEDING ON COURSE. WE ATTEMPTED THE FIRST 2 WITHOUT DME, THEN SWITCHED TO FO ALTERNATE GYRO. A SHORT TIME LATER AT 5000 FT OR 6000 FT, OUR TCASII SHOWED A TFC CONFLICT AT 3 O'CLOCK, SAME ALT, COMING TOWARD US (EBOUND). WHILE WE WERE ON COURSE PROCEEDING SBOUND ON OR NEAR THE COLTS NECK 350 DEG RADIAL, THE TCASII THEN GAVE A 'CLB' COMMAND. WX WAS MVFR. I BEGAN A SLIGHT 200-300 FT CLB WHILE OBSERVING TFC PASSING OFF OUR R AND BEHIND US WITHIN 2 MI. THE CAPT (PNF) NOTIFIED NEW YORK DEP OF OUR TCASII TFC AND INFORMED THEM WE WERE CLBING. ATC ACKNOWLEDGED AND APOLOGETICALLY INDICATED IT WAS THEIR ARR TFC INTO EWR. THEY THEN ASKED US TO RETURN TO ASSIGNED ALT WHEN ABLE DUE TO PASSING TFC ABOVE, FROM R TO L (W TO E) ABOVE US 1000 FT. WE COMPLIED. THE COCKPIT IN ALL THIS WAS EXTREMELY BUSY WITH CREW COORD REGARDING COLLISION AVOIDANCE MANEUVER, MULTIPLE COCKPIT INST FAILURE EARLIER, AND CONTINUING REAL TIME TFC OBSERVANCE IN THE VICINITY. SOMEWHERE AND SOMETIME SHORTLY AFTERWARDS, WE MAY HAVE OVERFLOWN A TURNPOINT AT WHITE INTXN TO INTERCEPT THE COYLE 226 DEG COURSE. ATC BY NOW HAD BEEN SWITCHED, WE THINK, TO ZNY OR ZDC, WHO WAS LIKELY UNAWARE OF OUR TCASII CONFLICT AND RESULTING DEV FROM FLT PATH. THIS COULD ONLY BE PREVENTED IN FUTURE BY THOROUGH COM BTWN ATC FACILITIES OR QUICKER PLT REACTION TO COURSE TRACKING WHILE IN THE MIDST (OR SHORTLY AFTER) OF AN EMER MANEUVER SIT. ALSO, IT WOULD HELP IF ATC WOULD CALL OR WARN ACFT IF THEY SENSE A POTENTIAL CONFLICT.
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.