Flugpark
Registration Login
Sortie: 21.03.2025 - 01:26 Dead
pilot: JG1_Maushake
Back to sorties list
01:26:30
respawn
01:28:26
takeoff
01:39:22
was damaged - 0.6%
BULLET_ENG_7-7X56_APSMK
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:39:22
was damaged - 0.1%
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:39:59
was damaged - 0.7%
2 X BULLET_ENG_7-7X56_APSMK
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:39:59
was damaged - 0.1%
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:39:59
was damaged - 0.1%
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:40:18
was damaged - 0.1%
2 X BULLET_ENG_7-7X56_APSMK
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:42:41
damaged - 0.9%
3 X MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:41
damaged - 0.1%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:42
damaged - 0.1%
4 X MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:42
damaged - 0.1%
3 X MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:42
damaged - 0.1%
2 X MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.8%
5 X MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.1%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.2%
MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
wounded - 58.2%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 7.1%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.9%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.1%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.8%
MG 17 (AP)
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:42:44
damaged - 0.1%
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:43:54
was damaged - 0.1%
BULLET_ENG_7-7X56_APSMK
NO.20_W_M_Thomson
Bristol F2B (F.III)
01:45:19
damage - 0.5%
01:45:19
damage - 1.0%
01:45:19
damage - 0.5%
01:45:19
damage - 0.1%
01:45:19
damage - 0.1%
01:45:19
damage - 0.1%
01:45:19
damage - 7.8%
01:45:19
damage - 88.2%
01:45:19
wound - 100.0%
01:45:19
DIED
01:45:19
end
01:45:21
WAS SHOTDOWN
NO.20_Krispy_Duck
Bristol F2B (F.III)
01:45:21
crashed
* 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.