Flugpark
Enregistrement Connexion
Sortie: 26.11.2023 - 21:30 Posé
pilot: No.10_KerzhMax
Retour à la liste des sorties
21:30:13
réapparition
21:30:40
décollage
21:33:29
a été endommagé - 0.1%
BULLET_ENG_7-7X56_APSMK
76SQN-FatherTed
Bristol F2B (F.II)
21:33:29
a été endommagé - 0.1%
BULLET_ENG_7-7X56_APSMK
76SQN-FatherTed
Bristol F2B (F.II)
21:33:52
endommagé - 0.1%
MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:52
endommagé - 0.7%
2 X MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:52
endommagé - 0.1%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:52
endommagé - 0.3%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:52
a été endommagé - 0.1%
2 X BULLET_ENG_7-7X56_APSMK
76SQN-Brazo
Bristol turret
21:33:53
endommagé - 0.2%
2 X MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:53
endommagé - 1.9%
MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:53
endommagé - 0.2%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:53
a été endommagé - 0.2%
BULLET_ENG_7-7X56_APSMK
76SQN-Brazo
Bristol turret
21:33:54
a été endommagé - 0.1%
BULLET_ENG_7-7X56_APSMK
76SQN-Brazo
Bristol turret
21:33:56
blessé - 40.8%
MG 17 (AP)
76SQN-Brazo
Bristol turret
21:33:56
blessé - 52.6%
5 X MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:56
endommagé - 6.4%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:56
endommagé - 0.8%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:56
endommagé - 0.1%
MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:57
endommagé - 0.1%
9 X MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
endommagé - 0.8%
6 X MG 17 (AP)
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
endommagé - 0.1%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
a été endommagé - 0.2%
2 X BULLET_ENG_7-7X56_APSMK
76SQN-Brazo
Bristol turret
21:33:58
endommagé - 84.3%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
ABATTU
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
blessé - 33.7%
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
TUE
76SQN-FatherTed
Bristol F2B (F.II)
21:33:58
a été endommagé - 0.2%
BULLET_ENG_7-7X56_APSMK
76SQN-Brazo
Bristol turret
21:37:13
atterrissage
21:37:43
fin
* Ammo types are not attached to damage logs in the log files. "Ammo hit" logs are attached via processing to damage logs using an educated guess, so it may be incorrect.