Narrative:

I was working D-45 combined with sector 46. I observed an uncorrelated target at 140 approaching my boundary. I waited to see what would happen since I know that there have been major issues with navy fallon's (nfl) new airspace. Navy fallon only owned approach control airspace which ends over 40 miles from our boundary with salt lake city. We; ZOA; owned desert's airspace which goes up to slc's boundary. Slc 43 called me when aircraft X was only about 1 mile from my boundary and still uncorrelated. They said I guess this is a point out; they had tried to call nfl with a hand off but they told slc they do not look out that far. I advised slc that we owned desert which went from the boundary to about 40 miles to the west and that aircraft X was radar contact. The slc controller said that they had been told when nfl approach was open that they owned the airspace up to their boundary. He said that he had initiated a hand off to 'O' and that it had auto flashed to nfl. This is obviously a dangerous situation; our computer and slc's computer have not been programmed correctly for this new split in airspace. We have had tens of problems with this separation of approach and desert. We were never briefed by airspace and procedures. Four new LOA's were put in place that were not explained to us. When we complained about them; one of them disappeared; so there are only 3 on record now. Recommendation; I would recommend that everyone involved with this airspace at ZOA and ZLC be properly briefed and that the computers be programmed correctly to allow for different ownership of desert's airspace. If this can not be done; I would recommend going back to where is nfl is open they own approach and desert.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZOA Controller described confused hand off attempt involving adjacent facilities claiming new airspace and procedures were not properly briefed and computers not programmed to accommodate airspace re-design.

Narrative: I was working D-45 combined with Sector 46. I observed an uncorrelated target at 140 approaching my boundary. I waited to see what would happen since I know that there have been major issues with Navy Fallon's (NFL) new airspace. Navy Fallon only owned approach control airspace which ends over 40 miles from our boundary with Salt Lake City. We; ZOA; owned Desert's airspace which goes up to SLC's boundary. SLC 43 called me when Aircraft X was only about 1 mile from my boundary and still uncorrelated. They said I guess this is a point out; they had tried to call NFL with a hand off but they told SLC they do not look out that far. I advised SLC that we owned Desert which went from the boundary to about 40 miles to the west and that Aircraft X was RADAR contact. The SLC Controller said that they had been told when NFL Approach was open that they owned the airspace up to their boundary. He said that he had initiated a hand off to 'O' and that it had auto flashed to NFL. This is obviously a dangerous situation; our computer and SLC's computer have not been programmed correctly for this new split in airspace. We have had tens of problems with this separation of Approach and Desert. We were never briefed by Airspace and Procedures. Four new LOA's were put in place that were not explained to us. When we complained about them; one of them disappeared; so there are only 3 on record now. Recommendation; I would recommend that everyone involved with this airspace at ZOA and ZLC be properly briefed and that the computers be programmed correctly to allow for different ownership of Desert's airspace. If this can not be done; I would recommend going back to where is NFL is open they own Approach and Desert.

Data retrieved from NASA's ASRS site as of April 2012 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.