Date: 202012
Local time of day: 1201-1800
Location: PBI.Airport, FL
Aircraft: Commercial Fixed Wing
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Fractional
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight; Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure; Human Factors
Primary problem: Human Factors

Narrative: We were given a recovery trip from PBI to ZZZ1. Upon arriving at the aircraft we had to defer the Nav database and the Jeppessen charts. We did just that which made us unable to do RNAV STARS; SIDS; routes etc. When the First Officer tried to get the clearance they gave us a RNAV SID and an AR route as that is what had been filed. The First Officer advised them we were unable to accept the route as we weren't able RNAV SIDS; STARS; routes etc. they informed us that our suffix indicated we were RNAV capable so we would have to refile correctly for us to go without using an RNAV SID. I called dispatch and explained it to the dispatcher and asked for it to be refiled with an appropriate route and suffix. It was refiled with a different route but the suffix still showed us as RNAV capable so clearance still wouldn't issue it. I called dispatch again and asked for it to be corrected and filed again. I made sure the third flight plan did come through with a different suffix before turning my attention to the passengers as they had now shown up. I greeted the owners and got them loaded and made sure the bags were loaded. During the baggage loading it became apparent I would have to increase the weight to match the weight of bags for the trip. I adjusted the weight in the waypoint app and waited for a valid release. The First Officer had briefed the passengers and we got into the cockpit and got ready to go while we waited for the release. We waited quite a while for the release as we began making phone calls and sending messages to try and see if the release was coming. Once I finally got through to the dispatcher on the phone and asked if the new release was coming soon. He responded 'what do you mean? You're in the air already.' I informed him that no we weren't we were still waiting on a valid release due to the weight change. Shortly after that we received a release from a different dispatcher which we verified the suffix was still the same as the last release and made our way to depart. A short time into the flight they gave us a reroute to a couple RNAV fixes and different route. We advised them we weren't RNAV and would like to remain on our route navigating by ground based navigation. It was at this point that I started to wonder if the suffix still wasn't correct for the airplanes condition. We continued without further issues. The entire process was truly exhausting having to review and keep straight in my head four releases and make sure they were done correctly; even if it wasn't already a new airplane as well as a recovery at the end of what was now becoming a long day. The last two releases being issued after the passengers were already onboard the airplane.




Synopsis: Captain reported difficulty with dispatch getting the correct aircraft suffix filed on the flight plan.