Date: 201810
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
ATC / advisory: CTAF ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness; Confusion
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; General Police / Security Involved
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Chart Or Publication

Narrative: Upon arrival at the Aircraft; the flight crew realized that the Tower had just closed making the airport environment uncontrolled and runway maintenance on the intended departure had just commenced. This caused us to use the smaller runway on the other side of the airport. Coming up with the taxi plan we elected to steer clear of runway maintenance since taxiway C was NOTAM'd closed; but the taxi route we chose would have taken us on taxiways that were too narrow for the A321. We began the taxi to runway XXL via A;D;K but the taxiway widths were poorly marked on the Jepp 10-9 and we didn't realize how narrow the taxiways were until the CA (Captain) was taxiing on A with intention of turning right on D but while passing the taxiway it was so narrow it appeared to be an access road and when the CA turned on to what he thought was taxiway D we were turning onto Runway YY. The only way to exit that runway at that point would have been Taxiway E which appeared to be just as narrow as taxiway D. The crew decided with Dispatch to shut down engines and call a tug to push us back to taxiway A. We made all the appropriate radio calls to keep any potential traffic from landing on Runway YY. We then started engines again and got a follow me from airport ops to 9L via A; Q and a backtaxi on XXL. Take off and departure was uneventful.Poorly notated company guidance with no taxiway widths. Little to no information from the company on Tower and Runway closures witch the company was unaware of.Update of [airport] pages or some company guidance with taxiway widths that are less than standard and Dispatch and company passing better information to crews when doing things that are non-standard ie night; unfamiliar airfields; unfamiliar and nonstandard taxi. A page sheet with some helpful tips on how to navigate a difficult and nonstandard environment would have been very helpful.


Second narrative: I was short call reserve. I was not given ANY information on nature of the mission; type of ferry; operational specifics; etc. I was lucky and able to self-print up a flight plan at the inbound gate before terminal was completely closed down. After a lengthy delay getting in contact with Wi-Fi installation contractor; my FO (First Officer) and I were picked up at terminal and taken to the jet (A-321). During preflight; ATIS stated tower was closed. ATIS also stated Main Runway (10;000ft) was also closed for scheduled maintenance. I called Dispatch and told them the only runway now available was XXL which is only 6000 feet long and across the field. Tried to look up minimum runway length limitations in FOM/OPs/OM with no results. Dispatch sent new take off data for short runway. Next we briefed a taxi route to far side of airport using Jepp Pro 10-9 plate considering ATIS announced closed runways and taxiways. On taxi out from the hangar ramp the taxi lights were minimal; and as we taxied off ramp to Taxiway Alpha to Delta to Kilo; I taxied from A; and past D because it is very narrow and looked like an access road. I then turned onto Runway YY which is parallel to Delta and Taxiway width. On the moving map it is so close to Delta that map icon looked correct. As soon as aircraft turned the corner onto Runway YY I realized the error but could not turn off the runway as we were too far off taxiway A and the end taxiway Echo is too narrow and too short for a mainline jet. We were now stuck on an active runway at an uncontrolled airport at night with no communication via radio to any controlling agency on the field. As we tried to raise anyone at the airport via radio and cellphone I turned on all exterior lighting and monitored Unicom to prevent an aircraft from trying to use the runway. We eventually made contact with airport police via radio; and the [FBO] contract personnel via cellphone through dispatch who then returned to the airport. [FBO] brought a tug and we were pushed and towed back onto taxiway A; where an airport personnel radio car then led us to Runway XXL via taxiway A to Q to the runway mid-length with a back taxi on the runway for full length take off. T/O and flight were normal. Dispatched to operate at night; at an unfamiliar Non-Mainline airport with a known Tower and runway closure. No special instructions for crew. No information on Jepp 10-9 plate with taxi width information and many taxiways too small for mainline jets.


Synopsis: A321 flight crew reported difficulty taxiing at an unfamiliar airfield due to a scheduled runway closure and lack of taxiway information.