B-767 first officer reported during cruise that flight crew was not accurately informed of actual dg...

Narrative:

Upon initial departure from ZZZ aircraft X was forced to return to the same gate due to a cargo loading issue. Because of the issue; no final weight manifest was delivered to the aircraft; although we had a final dg (dangeous goods) summary. Upon return to gate; some passengers requested to disembark. Cargo was verified and the close out was completed. Departure from the gate was accomplished with the confirmation that no dg was loaded in the bulk pit. Final weights were delayed due to a computer issue posting the weights to a now out of date flight on the second departure. Once final weights were delivered; ACARS was unable to retrieve T/O (takeoff) data due to several issues. Re-initialization of ACARS was attempted to fix the problem; unsuccessfully. Dispatch provided final weights; T/O data; and the flight departed. During the flight; the first officer (first officer) requested a final weights manifest for the flight to compare against what he thought was the initial [weight manifest]. Since there was never an initial [weight manifest]; the comparison was against the same document; although a final dg summary printed with this request. This resulted in a situation where the flight crew was not accurately informed of actual cargo loaded since we were informed there was no dg loaded in the bulk pit; yet still had a final dg loaded form with the [manifest].

Original NASA ASRS Text

Title: B-767 First Officer reported during cruise that flight crew was not accurately informed of actual DG cargo loaded after a ground gate return.

Narrative: Upon initial departure from ZZZ Aircraft X was forced to return to the same gate due to a cargo loading issue. Because of the issue; no final weight manifest was delivered to the aircraft; although we had a final DG (dangeous goods) summary. Upon return to gate; some passengers requested to disembark. Cargo was verified and the close out was completed. Departure from the gate was accomplished with the confirmation that no DG was loaded in the bulk pit. Final weights were delayed due to a computer issue posting the weights to a now out of date flight on the second departure. Once final weights were delivered; ACARS was unable to retrieve T/O (takeoff) data due to several issues. Re-initialization of ACARS was attempted to fix the problem; unsuccessfully. Dispatch provided final weights; T/O data; and the flight departed. During the flight; the FO (First Officer) requested a final weights manifest for the flight to compare against what he thought was the initial [weight manifest]. Since there was never an initial [weight manifest]; the comparison was against the same document; although a final DG summary printed with this request. This resulted in a situation where the flight crew was not accurately informed of actual cargo loaded since we were informed there was no DG loaded in the bulk pit; yet still had a Final DG Loaded form with the [manifest].

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	1735390
Time
Date	202003
Local Time Of Day	0001-0600
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B767 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Parked
Flight Plan	IFR
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 144
Events
Anomaly	Deviation - Procedural Hazardous Material Violation Deviation - Procedural Published Material / Policy Deviation - Procedural Weight And Balance

B-767 first officer reported during cruise that flight crew was not accurately informed of actual dg cargo loaded after a ground gate return.