Narrative:

As captain; I improperly identified the potomac river and aircraft in front of us after a very busy vectoring and speed sequences. To reduce some of our workload; I loaded several fixes into the FMS to facilitate the prohibited airspace issues within the dca environs. After being cleared for the river visual; the FMS did not sequence as anticipated and because I had misjudged the river; I subsequently overshot the river boundaries and entered P56-B. I initiated a turn to correct my error and at the same time potomac approach issued immediate turns and climbs to discontinue the approach.after our break off; we were being re-vectored; we were asked if we were ready to turn back in (I note this because this is an example of being rushed) and accept another approach. We communicated to continue on a heading for a little longer to complete our checklist and get set up for another try.it has been sometime since I have done the river visual 19 at night with the lighting effects and shadows. The jepp plate for river visual 19 notes the RNAV 19 which is not loaded in our database. This may be useful to look into to see if our databases can accept this. Also; on our other chart info (10-7 and other reference pages); we illustrate the dca-328 radial as a method of tracking for runway 1 departures. This could be used as a 'boundary' reference for inbound arrivals.I literally forgot about the black-hole this approach sometimes creates. Still; at my level of experience; I am quite disappointed. This event rests solely on my shoulders. Add in our [manual] pages to depict the dca-328 for RW19 arrivals and rw 1 arrivals/departures unless our FMS database can be updated. This should help reduce our P56 incursions.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight Crew and Controller reported of the flight being off course and entering Restricted Area P-56. Controller reported of aircraft being below the Minimum Vectoring Altitude and needing to vector aircraft out of P56. Pilot reported of improperly identifying the Potomac River and the aircraft to follow.

Narrative: As Captain; I improperly identified the Potomac River and aircraft in front of us after a very busy vectoring and speed sequences. To reduce some of our workload; I loaded several fixes into the FMS to facilitate the prohibited airspace issues within the DCA environs. After being cleared for the River Visual; the FMS did not sequence as anticipated and because I had misjudged the River; I subsequently overshot the river boundaries and entered P56-B. I initiated a turn to correct my error and at the same time Potomac Approach issued immediate turns and climbs to discontinue the approach.After our break off; we were being re-vectored; we were asked if we were ready to turn back in (I note this because this is an example of being rushed) and accept another approach. We communicated to continue on a heading for a little longer to complete our checklist and get set up for another try.It has been sometime since I have done the River Visual 19 at night with the lighting effects and shadows. The Jepp Plate for River Visual 19 notes the RNAV 19 which is not loaded in our database. This may be useful to look into to see if our databases can accept this. Also; on our other chart info (10-7 and other reference pages); we illustrate the DCA-328 radial as a method of tracking for RWY 1 departures. This could be used as a 'boundary' reference for inbound arrivals.I literally forgot about the black-hole this approach sometimes creates. Still; at my level of experience; I am quite disappointed. This event rests solely on my shoulders. Add in our [manual] pages to depict the DCA-328 for RW19 arrivals and RW 1 arrivals/departures unless our FMS database can be updated. This should help reduce our P56 incursions.

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.