37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 377866 |
Time | |
Date | 199708 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : dbq |
State Reference | IA |
Altitude | msl bound lower : 27500 msl bound upper : 28000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zau |
Operator | common carrier : air carrier |
Make Model Name | B767 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | descent other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | other other : other pilot : atp pilot : instrument pilot : flight engineer pilot : cfi |
Experience | flight time last 90 days : 150 flight time total : 12000 flight time type : 800 |
ASRS Report | 377866 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer pilot : cfi |
Experience | flight time last 90 days : 120 flight time total : 15000 flight time type : 450 |
ASRS Report | 377540 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude conflict : airborne less severe non adherence : clearance other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course flight crew : took evasive action |
Consequence | Other |
Miss Distance | horizontal : 5000 vertical : 1400 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation other |
Narrative:
We were cruising wbound at FL280 direct dbq VOR when ZAU gave us a heading vector of 230 degrees for traffic. Shortly thereafter a descending target at about 1 O'clock position set off a TA, and then as he was descending through FL294, we received an RA to descend. We followed the advisory to about FL275 whereupon conflict was resolved and returned to FL280. There was probably never any real traffic conflict. I think because the opposite direction traffic was descending at a fairly high rate to FL290 it triggered the TCASII resolution software.
Original NASA ASRS Text
Title: FLC OF A B767 DSNDED IN RESPONSE TO A TCASII RA FROM ANOTHER ACFT DSNDING FROM ABOVE.
Narrative: WE WERE CRUISING WBOUND AT FL280 DIRECT DBQ VOR WHEN ZAU GAVE US A HDG VECTOR OF 230 DEGS FOR TFC. SHORTLY THEREAFTER A DSNDING TARGET AT ABOUT 1 O'CLOCK POS SET OFF A TA, AND THEN AS HE WAS DSNDING THROUGH FL294, WE RECEIVED AN RA TO DSND. WE FOLLOWED THE ADVISORY TO ABOUT FL275 WHEREUPON CONFLICT WAS RESOLVED AND RETURNED TO FL280. THERE WAS PROBABLY NEVER ANY REAL TFC CONFLICT. I THINK BECAUSE THE OPPOSITE DIRECTION TFC WAS DSNDING AT A FAIRLY HIGH RATE TO FL290 IT TRIGGERED THE TCASII RESOLUTION SOFTWARE.
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.