ZLA controller reported an aircraft they assumed would continue on a southbound heading and turn aft...

Attributes
ACN	1280497
Time
Date	201507
Local Time Of Day	1801-2400
Place
Locale Reference	ZLA.ARTCC
State Reference	CA
Environment
Light	Night
Aircraft 1
Make Model Name	B737-800
Operating Under FAR Part	Part 129
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 24.25
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

The aircraft had filed to fly over tij; then UJ7 ppe. Tij is just outside my airspace by about 2 miles on the mexican side of the border. This routing that aircraft X had filed is unusual routing since it turns sharply to the east for 50 miles. Normally in this situation; the mmzt center controller will issue alternate routing instructions to let the aircraft to fly a more direct route. Since they almost always adjust unusual routing; I did not check what the aircraft had filed past tij and thought it was clear of all us airspace. Once the aircraft had crossed the border into mexico; my d-side dropped the data tag. The aircraft then turned east along his route; flying along the boundary of sector 31's airspace without an approved point-out. The sector 31 controller noticed the limited data block flying along his boundary; and brought it to my attention.I need to be sure to double check the routing after the first fix outside my airspace to ensure that I make all proper point-outs before dropping the data tag.

Original NASA ASRS Text

Title: ZLA Controller reported an aircraft they assumed would continue on a southbound heading and turn after leaving the US. The aircraft was not pointed out to the adjacent sector causing an airspace deviation.

Narrative: The aircraft had filed to fly over TIJ; then UJ7 PPE. TIJ is just outside my airspace by about 2 miles on the Mexican side of the border. This routing that Aircraft X had filed is unusual routing since it turns sharply to the East for 50 miles. Normally in this situation; the MMZT Center controller will issue alternate routing instructions to let the aircraft to fly a more direct route. Since they almost always adjust unusual routing; I did not check what the aircraft had filed past TIJ and thought it was clear of all US airspace. Once the aircraft had crossed the border into Mexico; my D-side dropped the data tag. The aircraft then turned east along his route; flying along the boundary of Sector 31's airspace without an approved Point-Out. The Sector 31 controller noticed the limited data block flying along his boundary; and brought it to my attention.I need to be sure to double check the routing after the first fix outside my airspace to ensure that I make all proper point-outs before dropping the data tag.

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

ZLA controller reported an aircraft they assumed would continue on a southbound heading and turn after leaving the us. The aircraft was not pointed out to the adjacent sector causing an airspace deviation.