Date: 201903
Local time of day: 0601-1200
Location: FAT.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class C FAT
ATC / advisory: Tower FAT
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors; Company Policy
Primary problem: Human Factors

Narrative: Taxied out to [Runway] 29L at KFAT. [Runway] 29R was closed. Still pretty dark; short taxi; unfamiliar with airport; one taxiway leads to both thresholds. While pulling up paperwork earlier; I assumed departure would be to the east due to wind. Discussed tailwind corrections on TPS and applied those with QRH input. First Officer's take-off. On rotation; I noted that we were a long way down the runway. Later on climb-out; First Officer re-checked TPS and discovered that we had used [Runway] 29R numbers instead of [Runway] 29L and that we were overweight for the runway at that flap and power setting. Inattention on my part to ensure that the correct numbers for the correct runway were being used. First Officer gave very thorough take off data and bugs brief and I missed that [Runway] 29R numbers had been entered in the CDU. [We] should have briefed the weight restrictions on [Runway] 29L more clearly.  Brief parallel runway TPS considerations and make a definite check that we had the correct numbers for the correct runway.


Second narrative: While on a short taxi out to Runway 29L in KFAT ([Runway] 29R closed). I reviewed and briefed the TPS data for [Runway] 29R to the Captain. Due to a slight tailwind; we reviewed tailwind corrections and used QRH numbers for the speeds. It was a longer takeoff roll than we expected. Later on the climb out; I reviewed the TPS and realized that I read the numbers for [Runway] 29R instead of [Runway] 29L to find out that we exceeded our 29L numbers for weight; flap and power setting. My mistake reading the [Runway] 29R data instead of [Runway] 29L.  [We should] have a more detailed discussion about parallel runways and runways that are in close proximity to one another. If they are close and one doesn't have good TPS data; pull up a good data for that Runway. Also; [have] the Captain 'verbally' agree and verify that I am reading the correct runway data for the runway we are actually taking off from.


Synopsis: B737 flight crew reported that they mistakenly used takeoff numbers for a runway which they did not use for takeoff; they were overweight for the runway at that flap and power setting they used.