Date: 202106
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion; Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure; Aircraft
Primary problem: Procedure

Narrative: This is an informative report to highlight an issue that could be a safety and or planning concern. We were planning our takeoff data for departing ZZZ and were receiving MTOG [Maximum Take Off Gross] limitations that seemed unusually restrictive. We were a full flight from ZZZ - ZZZ1 reasonable fuel load. The advertised runways in use for departure were Runway XX; XYL. We were unable to receive takeoff data for Runway XX at our weight. The restriction on MTOG was listed as Obstacle Limitation. We tried various adjustments to get a number that would work. We were able to get takeoff data for XYL but that was limited also. We were required to do a TOGA takeoff even at a medium weight in a 319. We were concerned why the takeoff was so limited on a relatively average day with moderate weight and favorable winds. It took several calls to Dispatch to confirm that the numbers were accurate. The Dispatcher was unable to find a reason for the restrictive data. As we found out later with the help of another flight that had departed ZZZ also that morning; there was an obstacle that seemed to be the reason. Although we read the NOTAMs for the field and noted the cranes; etc; construction obstacles for the various runways; what we didn't see was that these obstacles had a significant effect on takeoff data calculations. Normally we understand that when the review is done for takeoff performance evaluations the message is that if engineering has looked at it you are good to operate as normal with the possibility of effects on takeoff data. But this was a rather significant change to the takeoff data. We were concerned that as we were quite limited to which runway we were able to use safely it could become very restrictive if conditions were less favorable. For example; heavier weight; tailwind; hotter temps. Our main concern was that there was no information to pre-plan for this restrictive data. The point of this report is to provide the information from our experience for future flights. It seemed like information from operations would have been appropriate to help us plan for and minimize threats to our takeoff planning. We wanted to encourage a further look at this threat with the intent to warn other crews of the more complicated takeoff restrictions departing ZZZ.


Second narrative: Preflight planning had us plan for Runway XX departure. ATIS confirmed that. Computer came back with MTOG of 127.0 max for Runway XX.  So we planned for Runway XYL. Also got an error for 151.0 weight on that runway.  We finally got a valid takeoff condition doing TOGA takeoff at 148.5.  Called Dispatch and they saw the same limits in computer.  If the wind was stronger out of the west I [was] sure we would be able to takeoff.  Meanwhile we saw 2 A319's from other airlines takeoff Runway XX.


Synopsis: Pilots reported unusual restrictive take off weights for the runways in use.