37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 283780 |
Time | |
Date | 199409 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : hct |
State Reference | NE |
Altitude | msl bound lower : 33000 msl bound upper : 35300 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zdv |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller non radar : 3 controller radar : 1 |
ASRS Report | 283780 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude non adherence : clearance other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | Pilot Deviation |
Narrative:
Air carrier X was flying east bound to jot en route to cyul. The aircraft was at the hct 118 047 when I observed the aircraft climbing out of FL330 through FL340, moments later the pilot of X advised me that he was responding to a TCASII advisory to climb at 3000 FPM for traffic. I acknowledged the pilot and told him the only aircraft in the area was 11 O'clock and 20 mi FL350. He climbed to 353 before descending back to 330, saying it was a false alert, the traffic was same altitude and no lateral but seemed to be tracking exactly with them. He said he would have the TCASII checked when he landed. The pilots of aircraft responding to TCASII advisories need to be aware that there is a lot of traffic out there and it is very dangerous to just respond to advisories without advising ATC first, especially in the positive control area where all aircraft are in contact with ATC.
Original NASA ASRS Text
Title: ACR X FALSE TCASII RA UNAUTH CLB FROM ASSIGNED ALT.
Narrative: ACR X WAS FLYING E BOUND TO JOT ENRTE TO CYUL. THE ACFT WAS AT THE HCT 118 047 WHEN I OBSERVED THE ACFT CLBING OUT OF FL330 THROUGH FL340, MOMENTS LATER THE PLT OF X ADVISED ME THAT HE WAS RESPONDING TO A TCASII ADVISORY TO CLB AT 3000 FPM FOR TFC. I ACKNOWLEDGED THE PLT AND TOLD HIM THE ONLY ACFT IN THE AREA WAS 11 O'CLOCK AND 20 MI FL350. HE CLBED TO 353 BEFORE DSNDING BACK TO 330, SAYING IT WAS A FALSE ALERT, THE TFC WAS SAME ALT AND NO LATERAL BUT SEEMED TO BE TRACKING EXACTLY WITH THEM. HE SAID HE WOULD HAVE THE TCASII CHKED WHEN HE LANDED. THE PLTS OF ACFT RESPONDING TO TCASII ADVISORIES NEED TO BE AWARE THAT THERE IS A LOT OF TFC OUT THERE AND IT IS VERY DANGEROUS TO JUST RESPOND TO ADVISORIES WITHOUT ADVISING ATC FIRST, ESPECIALLY IN THE PCA WHERE ALL ACFT ARE IN CONTACT WITH ATC.
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.