37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 576190 |
Time | |
Date | 200303 |
Day | Tue |
Local Time Of Day | 0601 To 1200 |
Place | |
State Reference | MA |
Altitude | msl single value : 24000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zbw.artcc tower : ilm.tower |
Operator | common carrier : air carrier |
Make Model Name | A321 |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zbw.artcc |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : handoff position controller : departure controller : radar |
Qualification | controller : radar pilot : instrument |
Experience | controller radar : 21 controller time certified in position1 : 18 flight time total : 2500 |
ASRS Report | 576190 |
Person 2 | |
Affiliation | government : faa |
Function | controller : handoff position controller : radar |
Events | |
Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | none taken : insufficient time |
Consequence | faa : investigated |
Miss Distance | horizontal : 24000 vertical : 400 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Intra Facility Coordination Failure Operational Error |
Narrative:
I was the radar controller at the bosox sector. During my time at this position, I was involved in a situation concerning air carrier X and air carrier Y. Air carrier X was a bos departure, flight planned via center. I handled air carrier X normally including using an automated information handoff/xfer procedure with sector 46. During this time, I received a pointout from sector 36, the gardner sector, on air carrier Y, a mht departure en route to iad. I approved the pointout on air carrier Y from sector 36 stating in my approval, FL230. Shortly after approving the pointout on air carrier Y, I saw the interim altitude of FL230 had been removed from the data block of air carrier Y, and that the assigned altitude of FL280 was now displayed. I called sector 36 and asked them to assign FL230 to air carrier Y. It was agreed that air carrier Y would be issued FL230, and that I would work air carrier Y. Air carrier Y checked on my frequency, a speed restr for spacing to iad was issued due to traffic virtually overhead air carrier Y, also en route to iad. As air carrier Y approached air carrier X, I issued traffic. Shortly thereafter, I observed air carrier Y behind air carrier X and at FL233 or thereabouts, and asked the pilot to verify altitude. The pilot stated FL280. Air carrier Y had completely diverged from air carrier X, and presented no further traffic threat. My priority of duty was to insure separation between air carrier Y and air carrier Z, an aircraft laterally to the south of air carrier Y and above air carrier Y, and to insure that sector 46 was aware that air carrier Y was above its displayed interim altitude.
Original NASA ASRS Text
Title: ZBW CTLR FAILS TO COMPLY WITH COORD AUTOMATED INFO HDOF/ TRANSFER PROC, RESULTING IN AN OPERROR BTWN AN A321 AND A CARJ.
Narrative: I WAS THE RADAR CTLR AT THE BOSOX SECTOR. DURING MY TIME AT THIS POS, I WAS INVOLVED IN A SIT CONCERNING ACR X AND ACR Y. ACR X WAS A BOS DEP, FLT PLANNED VIA CTR. I HANDLED ACR X NORMALLY INCLUDING USING AN AUTOMATED INFO HDOF/XFER PROC WITH SECTOR 46. DURING THIS TIME, I RECEIVED A POINTOUT FROM SECTOR 36, THE GARDNER SECTOR, ON ACR Y, A MHT DEP ENRTE TO IAD. I APPROVED THE POINTOUT ON ACR Y FROM SECTOR 36 STATING IN MY APPROVAL, FL230. SHORTLY AFTER APPROVING THE POINTOUT ON ACR Y, I SAW THE INTERIM ALT OF FL230 HAD BEEN REMOVED FROM THE DATA BLOCK OF ACR Y, AND THAT THE ASSIGNED ALT OF FL280 WAS NOW DISPLAYED. I CALLED SECTOR 36 AND ASKED THEM TO ASSIGN FL230 TO ACR Y. IT WAS AGREED THAT ACR Y WOULD BE ISSUED FL230, AND THAT I WOULD WORK ACR Y. ACR Y CHKED ON MY FREQ, A SPD RESTR FOR SPACING TO IAD WAS ISSUED DUE TO TFC VIRTUALLY OVERHEAD ACR Y, ALSO ENRTE TO IAD. AS ACR Y APCHED ACR X, I ISSUED TFC. SHORTLY THEREAFTER, I OBSERVED ACR Y BEHIND ACR X AND AT FL233 OR THEREABOUTS, AND ASKED THE PLT TO VERIFY ALT. THE PLT STATED FL280. ACR Y HAD COMPLETELY DIVERGED FROM ACR X, AND PRESENTED NO FURTHER TFC THREAT. MY PRIORITY OF DUTY WAS TO INSURE SEPARATION BTWN ACR Y AND ACR Z, AN ACFT LATERALLY TO THE S OF ACR Y AND ABOVE ACR Y, AND TO INSURE THAT SECTOR 46 WAS AWARE THAT ACR Y WAS ABOVE ITS DISPLAYED INTERIM ALT.
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.