37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 689484 |
Time | |
Date | 200602 |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | intersection : sardi |
State Reference | NY |
Altitude | msl single value : 9000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zbw.artcc artcc : zny.artcc |
Operator | general aviation : personal |
Make Model Name | Falcon 50 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 23 |
ASRS Report | 689484 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Deviation |
Narrative:
I was working the ZBW sardi sector; position #32; radar; combined with the ZBW hampton sector; position #31; combined at position #32. After a flurry of traffic involving international overflt; international departure traffic from the new york metropolitan area; and various other aircraft; I became aware of a limited data block in the vicinity of the sardi intersection; level at 9000 ft. At that moment; aircraft X; a T/FA50/K called on to my frequency level at 9000 ft. I had no computer flight data on this aircraft and after acknowledging aircraft X on frequency I called ZNY; manta sector; and asked if they had flight data on the aircraft. I received the minimum amount of information necessary to handle the aircraft; and also communicated with N90; to confirm that they had flight data. A handoff was completed to N90. Reference aircraft X; no airspace violation took place nor were any separation standards compromised. The supervisor on duty for the shift received a brief description of the event with an accompanying explanation that no airspace or separation standards were compromised and that I as the controller of the sector had had no problem handling the aircraft; nor any issues with ZNY.
Original NASA ASRS Text
Title: AN IFR FA50 ACFT ENTERS A CTLR'S ASSIGNED AIRSPACE WITHOUT COORD.
Narrative: I WAS WORKING THE ZBW SARDI SECTOR; POS #32; RADAR; COMBINED WITH THE ZBW HAMPTON SECTOR; POS #31; COMBINED AT POS #32. AFTER A FLURRY OF TFC INVOLVING INTL OVERFLT; INTL DEP TFC FROM THE NEW YORK METROPOLITAN AREA; AND VARIOUS OTHER ACFT; I BECAME AWARE OF A LIMITED DATA BLOCK IN THE VICINITY OF THE SARDI INTXN; LEVEL AT 9000 FT. AT THAT MOMENT; ACFT X; A T/FA50/K CALLED ON TO MY FREQ LEVEL AT 9000 FT. I HAD NO COMPUTER FLT DATA ON THIS ACFT AND AFTER ACKNOWLEDGING ACFT X ON FREQ I CALLED ZNY; MANTA SECTOR; AND ASKED IF THEY HAD FLT DATA ON THE ACFT. I RECEIVED THE MINIMUM AMOUNT OF INFO NECESSARY TO HANDLE THE ACFT; AND ALSO COMMUNICATED WITH N90; TO CONFIRM THAT THEY HAD FLT DATA. A HDOF WAS COMPLETED TO N90. REF ACFT X; NO AIRSPACE VIOLATION TOOK PLACE NOR WERE ANY SEPARATION STANDARDS COMPROMISED. THE SUPVR ON DUTY FOR THE SHIFT RECEIVED A BRIEF DESCRIPTION OF THE EVENT WITH AN ACCOMPANYING EXPLANATION THAT NO AIRSPACE OR SEPARATION STANDARDS WERE COMPROMISED AND THAT I AS THE CTLR OF THE SECTOR HAD HAD NO PROB HANDLING THE ACFT; NOR ANY ISSUES WITH ZNY.
Data retrieved from NASA's ASRS site as of January 2009 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.