Reporter states that on 2 separate occasions, aircraft that were under his control were less than 2 ...

Attributes
ACN	427663
Time
Date	199902
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : bgm
State Reference	NY
Altitude	msl bound lower : 17000 msl bound upper : 20000
Environment
Light	Daylight
Aircraft 1
Operator	other
Make Model Name	Thunderbolt II (Warthog A-10)
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Experience	controller military : 7 controller radar : 24
ASRS Report	427663
Person 2
Affiliation	government : faa
Function	controller : radar instruction : instructor
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact other
Consequence	Other
Supplementary
Air Traffic Incident	Operational Deviation

Narrative:

On feb/xa/99 I (person 1) was training at radar sector R50 with instructor (person 2). I am recertifying at the position because my training was stopped for a yr. Instructor (person 4) was working my handoff position, RA50. He was training person 3. 2 possible operational deviations occurred during the training session. A minimum of 6 controllers knew about the deviations, and one of them reported the deviations. Attached is a copy of an ATC strip on aircraft X. The time was around XA00Z when the aircraft almost entered radar sector R35's airspace. I asked person 4 and person 3, had they made a pointout to sector R35. At that time person 3 called the sector to make a pointout. The aircraft was well within 2.5 mi of sector R35's airspace. Unless ZBW gave sector R35 a pointout to turn the aircraft, an operational deviation occurred. Around 10 mins prior to this incident, the first operational deviation occurred. I do not remember the call sign of the aircraft because someone had taken the ATC strip. I could not find the strip to make a copy of it. Aircraft Y was a flight landing syracuse, ny. The aircraft was going direct bgm VOR about 30 mi south of it. I observed the aircraft very close to radar sector R51's airspace. I can be heard on the ATC tape giving the aircraft a left turn of 10 degrees to stay in my airspace. When person 3 heard me give the aircraft a turn, he called sector R51 with a pointout. Person 4, who was instructing person 3, asked me, could he use my range bearing radar equipment. He measured the distance from the aircraft to sector R51's boundary. He told person 3 that it was 2.1 mi and that it was too close. An operational deviation had occurred. Traffic was moderate to heavy during the training session. I started out by helping person 3 with his duties. I was told by my handoff position, that they wanted to perform their job without any help.

Original NASA ASRS Text

Title: RPTR STATES THAT ON 2 SEPARATE OCCASIONS, ACFT THAT WERE UNDER HIS CTL WERE LESS THAN 2 PT 5 MI FROM THE BOUNDARY OF AN ADJACENT SECTOR WITHOUT A POINTOUT. THIS IS CONTRARY TO THE FAA HANDBOOK, PARAGRAPH 5-5-9.

Narrative: ON FEB/XA/99 I (PERSON 1) WAS TRAINING AT RADAR SECTOR R50 WITH INSTRUCTOR (PERSON 2). I AM RECERTIFYING AT THE POS BECAUSE MY TRAINING WAS STOPPED FOR A YR. INSTRUCTOR (PERSON 4) WAS WORKING MY HDOF POS, RA50. HE WAS TRAINING PERSON 3. 2 POSSIBLE OPERATIONAL DEVS OCCURRED DURING THE TRAINING SESSION. A MINIMUM OF 6 CTLRS KNEW ABOUT THE DEVS, AND ONE OF THEM RPTED THE DEVS. ATTACHED IS A COPY OF AN ATC STRIP ON ACFT X. THE TIME WAS AROUND XA00Z WHEN THE ACFT ALMOST ENTERED RADAR SECTOR R35'S AIRSPACE. I ASKED PERSON 4 AND PERSON 3, HAD THEY MADE A POINTOUT TO SECTOR R35. AT THAT TIME PERSON 3 CALLED THE SECTOR TO MAKE A POINTOUT. THE ACFT WAS WELL WITHIN 2.5 MI OF SECTOR R35'S AIRSPACE. UNLESS ZBW GAVE SECTOR R35 A POINTOUT TO TURN THE ACFT, AN OPDEV OCCURRED. AROUND 10 MINS PRIOR TO THIS INCIDENT, THE FIRST OPDEV OCCURRED. I DO NOT REMEMBER THE CALL SIGN OF THE ACFT BECAUSE SOMEONE HAD TAKEN THE ATC STRIP. I COULD NOT FIND THE STRIP TO MAKE A COPY OF IT. ACFT Y WAS A FLT LNDG SYRACUSE, NY. THE ACFT WAS GOING DIRECT BGM VOR ABOUT 30 MI S OF IT. I OBSERVED THE ACFT VERY CLOSE TO RADAR SECTOR R51'S AIRSPACE. I CAN BE HEARD ON THE ATC TAPE GIVING THE ACFT A L TURN OF 10 DEGS TO STAY IN MY AIRSPACE. WHEN PERSON 3 HEARD ME GIVE THE ACFT A TURN, HE CALLED SECTOR R51 WITH A POINTOUT. PERSON 4, WHO WAS INSTRUCTING PERSON 3, ASKED ME, COULD HE USE MY RANGE BEARING RADAR EQUIP. HE MEASURED THE DISTANCE FROM THE ACFT TO SECTOR R51'S BOUNDARY. HE TOLD PERSON 3 THAT IT WAS 2.1 MI AND THAT IT WAS TOO CLOSE. AN OPDEV HAD OCCURRED. TFC WAS MODERATE TO HVY DURING THE TRAINING SESSION. I STARTED OUT BY HELPING PERSON 3 WITH HIS DUTIES. I WAS TOLD BY MY HDOF POS, THAT THEY WANTED TO PERFORM THEIR JOB WITHOUT ANY HELP.

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.

Reporter states that on 2 separate occasions, aircraft that were under his control were less than 2 pt 5 mi from the boundary of an adjacent sector without a pointout. This is contrary to the FAA handbook, paragraph 5-5-9.