Date: 201906
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Fuselage Attachment
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Trainee; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface; Distraction; Confusion; Communication Breakdown; Situational Awareness; Time Pressure; Workload
Second reporter function: Instructor; Pilot Not Flying; Captain
Anomaly: Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Landed As Precaution; Flight Crew Diverted; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Airport; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I was a prospective LCA (Line Check Airman) in training in the right seat of Aircraft X from ZZZ. Departing from gate.  This was my fifth right seat leg in the LCA training. My first leg out of ZZZ and on this ID. All preparations flows and checklists went well and the performance data was loaded for a reduced takeoff from XYR at [taxiway]. The final WT manifest showed:TOG: 159234TOW CHG: -615 ZFW: 130634 CG: 23.6 TAKEOFF DATA MSG SHOWED: 3KT HEADWIND 8KT CROSSWIND TOCG/TRIM 23.6 REDUCED NUMBERS WERE V1 147 VR 149 V2 153 On taxiout we were given taxi instructions for a XXL Departure. RWY XXL via [taxi route]. [En route during taxi] I reported going heads down to load the new runway and get new performance numbers. Ground traffic was light with minimal delays and minor ATC distractions encountered except for slowing to wait for a maintenance truck to move off and clear to the right as we turned onto Victor taxiway. The new runway was loaded; Performance requested and loaded; checklists completed; lineup and wait and takeoff clearance given. Takeoff roll and call outs were normal. As I recall; after the rotate call; the rotation felt normal. With the wheels still on the runway; and as rotation continued I felt an abnormal thump. We became airborne; began to climb and raised the gear. Initially; the Captain thought we must have blown a tire on the right side and reported that possibility to the tower. We noted that the gear came up normally and that all the gear lights were out (normal indications). Tower informed us they would inspect the runway and report the results through ATC.I thought initially that it might be due to dissipating wingtip vortices from a B777 that had landed recently on XYC [intersecting runway]. While waiting for a response from ATC the Captain called the flight attendants and ask if they felt the same anomaly. They confirmed that they felt the thump. We both suspected that ATC would confirm a tire failure. Somewhere close to the top of climb (FL340) ATC passed the word that ZZZ had completed a runway sweep and that no tire debris was located. We began to troubleshoot other options. Bird strike and cargo shift were briefly discussed and dismissed. I briefly considered tail strike but since my tendency is to rotate between 2-2.5 degrees per second; and my departure pitch is normally between 5-5.9 degrees (I can never recall more than 6.3 degrees); I thought it unlikely. However; since we were still stymied by the lack of tire failure confirmation I checked the [Flight Data Unit]. To my surprise Departure pitch was 11.2 degrees. On a B737-800 tail strike can occur at 11 degrees. I reported the discovery to the Captain and he immediately informed Dispatch as I pulled out the QRH. The Captain suggested a return to ZZZ (nearest suitable). Dispatch wanted a Conference Call with [Maintenance Control] and the [Chief Pilot]. Ultimately the decision was made to divert to ZZZ1 (nearest suitable after the conference call).The landing in ZZZ1 was uneventful and upon gate arrival maintenance confirmed a tail strike with the tail shoe scraped. Red and green lines remained visible on the cartridge. While airborne and after we determined that a tail strike was the suspected event I retrieved all of the departure paperwork and reviewed it for errors or anomalies. What I found was: TAKEOFF DATA FOR RWY XXL that was loaded AND EXECUTED was: 8KT HW 3KT XW CG 23.6 FLAPS 5 BLEEDS ON ASSUMED WT 130.8ASSUMED TEMP 65CREDUCED EPR 89.8V1 127 VR 133 V2 138I had loaded and requested ZFW as my TOG wt. What's worse is that after executing those TO speeds we received an ACARS msg that said: ************WARNING'************ REQUESTED TAKEOFF DATA MESSAGE ASSUMED WT 130.8 LESS THAN FINAL WEIGHT MANIFEST TOG 159.3 I recall getting that message about the time the maintenance truck was becoming an issue. WhenI returned to look at the message my eyes went straight to 130.8 and I failed to read the entire message. I confirmed 130.8 on the TOW page and accepted and executed the speeds for takeoff.This was clearly a costly error on my part and I make no excuses for my lack of attention to detail in this matter. Lack of experience in the right seat and ACARS performance work is no excuse. I also should have shown the Captain the message which would have slowed me down and; I am confident; would have prevented the tail strike.


Second narrative: I am a Line Check Airman; during this event I was performing right seat training for a new LCA (Line Check Airman.) We had planned departing off of runway XYR and programmed the FMC. During taxi we were advised of the runway change and [the FO (First Officer)] went heads down to begin working on the task. We had to respond to a couple of instructions from the ground controller that required his attention. When [the FO] was inputting our weight into the ACARS Take Off data page (see attached) he did not enter the correct aircraft weight and our V-speeds were significantly less than what they should have been for our actual weight.When the tailstrike occurred I initially thought we had blown a tire. We both heard and felt a soft thump. I asked the tower to inspect the runway for evidence of the blown tire and they responded that he would and the TRACON would advise us of what they found. Several minutes past and the Center controller advised us that they did not find any evidence of a blown tire. We considered other threats to and ruled them out. Bird strikes; cargo shift. After ruling those threats out [the FO] check the ACARS [Flight Data Unit] pitch report and it was 11.1 degrees. I called the flight attendants and asked them if they had felt or heard anything and they responded that; yes they heard and felt the noise but weren't sure what it was. [The FO] and I looked at the tail strike QRH checklist. The checklist said to not pressurize the airplane and land at the nearest suitable airport. We were already at cruise at FL340. I contacted our Dispatcher (see attached) and he arranged a conference call with the [Chief Pilot]; [Maintenance Control]; and the Fleet Technical advisor. After discussing the issue at length we agreed it continue to [our destination]. At this point we were abeam ZZZ1 and I made the decision to divert there to have the aircraft inspected (see attached) instead of continuing to [our destination]. We landed uneventfully and continued to our destination.


Synopsis: B737 flight crew reported tailstrike after having loaded incorrect takeoff data that went undiscovered.