Light Transport; High Wing; 2 Turboprop Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 2.5
Communication Breakdown; Confusion; Training / Qualification
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert
Human Factors; Airspace Structure; Procedure
Shortly after taking position; ZDC ENO called for a late point out.  Aircraft X was already in my airspace descending out of 105 [10;500 feet] on V229 northeast of PXT.  The ZDC controller explained he forgot to flash the plane.  I said point out approved to 90 [9;000 feet].  Aircraft X leveled at 90 and proceeded through GRACO airspace before re-entering ENO.  GRACO called and asked me if I was working Aircraft X after he was a few miles in their airspace.  I explained the situation and asked if ZDC had pointed him out (they hadn't); then I pointed out the aircraft to GRACO.  No other traffic was in the area.I was previously familiar with the rule that the ZDC LOA requires the facility that takes the point out to handle all intra-facility coordinations; but prior to accepting the new CSIDE airspace; this was rarely an occurrence in my area because the airspace was structured in a way that it wasn't necessary.  Since it wasn't something I was used to doing; it didn't occur to me to make the coordination to GRACO as I assumed ENO would do it. Most controllers are probably familiar with the LOA requirement to ensure all intra-facility coordination; but this was a good reminder for me.  Had I taken more time to re-read the entire ZDC LOA; rather than just the new sections pertaining to Optimization of Airspace and Procedures in the Metroplex (OAPM); I probably wouldn't have made this mistake.
PCT Controller reports of an aircraft that entered his sector with a late point out from ZDC; which later crosses onto another sector. Reporter realizes he should have pointed this aircraft out to the other sector in PCT's airspace.