37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 385909 |
Time | |
Date | 199711 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : mmj airport : pit |
State Reference | PA |
Altitude | msl bound lower : 6000 msl bound upper : 6000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pit |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Navigation In Use | Other Other |
Flight Phase | cruise other descent : approach descent other |
Route In Use | arrival other enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Navigation In Use | Other Other |
Flight Phase | cruise other descent other |
Route In Use | arrival other enroute : 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 : 200 flight time total : 12000 |
ASRS Report | 385909 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 250 flight time total : 10000 |
ASRS Report | 385908 |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 5999 vertical : 100 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
2 NM from nesto intersection, cleared to fly heading 300 degrees, cross grunz 6000 ft or above and cleared ILS runway 32 pit. 1 mi right of localizer and 1 1/2 degrees below GS at 6000 ft, ATC issued a turn to 360 degrees. We had an aircraft on TCASII 10 mi range approaching from 11 O'clock and 200 ft above. During the turn to 360 degrees we received an RA to descend which we followed. We notified controller of RA descent and he said 'do not descend.' aircraft on TCASII was still only 200 ft above and almost merged with us. We received a reduced descent followed by another RA descent. We followed second RA and aircraft passed 200 ft over top of us, then a clear of conflict was received. Initial descent was 800 ft to approximately 5200 ft and second descent was to around 4600 ft. We talked to pit approach supervisor on ground and he said the traffic was supposed to turn in front of us on approach. He said the traffic was turning too slow. He also said the commuter pilot said he received an RA climb at 5300 ft but we never saw any evidence of him climbing. He was following us down. I feel the TCASII saved a collision. The other aircraft was on a different frequency so we could not hear him respond to the controller. He could not hear us giving an RA descent to ATC either. I do not know why they were using different frequency in approach environment. Another point is if we had listened to the controller and followed his 'do not descend,' we probably would have collided. The supervisor said we were correct in following the RA and did not know how to classify the incident. He said it was a TCASII problem (?). I feel the controller is responsible for maintaining separation. Supplemental information from acn 385908: still closing, ATC turns us to a 360 degree heading. Our RA reacts at about the same time, 'descend, descend.' we follow TCASII order. We notify ATC of our RA descent. It appeared that our targets merged on our TCASII. During descent the target stayed on top of us indicating +200 ft. Supplemental information from acn 385758: while being radar vectored for the ILS runway 32 pit, a TCASII RA was received. Our flight was assigned a heading of 160 degrees for a left downwind pattern to parallel the localizer. On the west side of localizer the other aircraft, a B737, was between grunz and wyler on the runway 32 localizer at 6000 ft. We were then given a heading of left to 350 degrees and descend from 6000 ft to 4000 ft, expedite through 5000 ft. While in the turn passing through approximately 5500 ft, a TA was received, immediately followed by an RA to climb. As we initiated a leveloff followed by a climb, we noticed that the B737 was also descending with us. We climbed to approximately 5700 ft as the B737 continued to descend resolving the conflict. We feel the contributing factor to this event was our assigned turn to 350 degrees directly towards the B737 without the vertical separation.
Original NASA ASRS Text
Title: RPTED SIT OF A COMMUTER TURBOPROP AND AN ACR B737 CONVERGING AND DSNDING FROM THE SAME ALT RESULTING IN A LOSS OF SEPARATION AND BOTH ACFT REACTING TO TCASII RA EVASIVE ACTION COMMANDS. THE TURBOPROP CLBS AND THE B737 DSNDS.
Narrative: 2 NM FROM NESTO INTXN, CLRED TO FLY HDG 300 DEGS, CROSS GRUNZ 6000 FT OR ABOVE AND CLRED ILS RWY 32 PIT. 1 MI R OF LOC AND 1 1/2 DEGS BELOW GS AT 6000 FT, ATC ISSUED A TURN TO 360 DEGS. WE HAD AN ACFT ON TCASII 10 MI RANGE APCHING FROM 11 O'CLOCK AND 200 FT ABOVE. DURING THE TURN TO 360 DEGS WE RECEIVED AN RA TO DSND WHICH WE FOLLOWED. WE NOTIFIED CTLR OF RA DSCNT AND HE SAID 'DO NOT DSND.' ACFT ON TCASII WAS STILL ONLY 200 FT ABOVE AND ALMOST MERGED WITH US. WE RECEIVED A REDUCED DSCNT FOLLOWED BY ANOTHER RA DSCNT. WE FOLLOWED SECOND RA AND ACFT PASSED 200 FT OVER TOP OF US, THEN A CLR OF CONFLICT WAS RECEIVED. INITIAL DSCNT WAS 800 FT TO APPROX 5200 FT AND SECOND DSCNT WAS TO AROUND 4600 FT. WE TALKED TO PIT APCH SUPVR ON GND AND HE SAID THE TFC WAS SUPPOSED TO TURN IN FRONT OF US ON APCH. HE SAID THE TFC WAS TURNING TOO SLOW. HE ALSO SAID THE COMMUTER PLT SAID HE RECEIVED AN RA CLB AT 5300 FT BUT WE NEVER SAW ANY EVIDENCE OF HIM CLBING. HE WAS FOLLOWING US DOWN. I FEEL THE TCASII SAVED A COLLISION. THE OTHER ACFT WAS ON A DIFFERENT FREQ SO WE COULD NOT HEAR HIM RESPOND TO THE CTLR. HE COULD NOT HEAR US GIVING AN RA DSCNT TO ATC EITHER. I DO NOT KNOW WHY THEY WERE USING DIFFERENT FREQ IN APCH ENVIRONMENT. ANOTHER POINT IS IF WE HAD LISTENED TO THE CTLR AND FOLLOWED HIS 'DO NOT DSND,' WE PROBABLY WOULD HAVE COLLIDED. THE SUPVR SAID WE WERE CORRECT IN FOLLOWING THE RA AND DID NOT KNOW HOW TO CLASSIFY THE INCIDENT. HE SAID IT WAS A TCASII PROB (?). I FEEL THE CTLR IS RESPONSIBLE FOR MAINTAINING SEPARATION. SUPPLEMENTAL INFO FROM ACN 385908: STILL CLOSING, ATC TURNS US TO A 360 DEG HDG. OUR RA REACTS AT ABOUT THE SAME TIME, 'DSND, DSND.' WE FOLLOW TCASII ORDER. WE NOTIFY ATC OF OUR RA DSCNT. IT APPEARED THAT OUR TARGETS MERGED ON OUR TCASII. DURING DSCNT THE TARGET STAYED ON TOP OF US INDICATING +200 FT. SUPPLEMENTAL INFO FROM ACN 385758: WHILE BEING RADAR VECTORED FOR THE ILS RWY 32 PIT, A TCASII RA WAS RECEIVED. OUR FLT WAS ASSIGNED A HDG OF 160 DEGS FOR A L DOWNWIND PATTERN TO PARALLEL THE LOC. ON THE W SIDE OF LOC THE OTHER ACFT, A B737, WAS BTWN GRUNZ AND WYLER ON THE RWY 32 LOC AT 6000 FT. WE WERE THEN GIVEN A HDG OF L TO 350 DEGS AND DSND FROM 6000 FT TO 4000 FT, EXPEDITE THROUGH 5000 FT. WHILE IN THE TURN PASSING THROUGH APPROX 5500 FT, A TA WAS RECEIVED, IMMEDIATELY FOLLOWED BY AN RA TO CLB. AS WE INITIATED A LEVELOFF FOLLOWED BY A CLB, WE NOTICED THAT THE B737 WAS ALSO DSNDING WITH US. WE CLBED TO APPROX 5700 FT AS THE B737 CONTINUED TO DSND RESOLVING THE CONFLICT. WE FEEL THE CONTRIBUTING FACTOR TO THIS EVENT WAS OUR ASSIGNED TURN TO 350 DEGS DIRECTLY TOWARDS THE B737 WITHOUT THE VERT SEPARATION.
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.