Flugpark
Registration Login
Sortie: 28.02.2020 - 17:59 Disconnect
pilot: J37_Spyboy
Back to sorties list
{% trans 'The results of this sortie are not included in the statistics of the pilot because of the disconnect' %}
17:59:35
respawn
18:00:31
takeoff
18:17:36
was damaged - 0.1%
AI
Bristol turret
18:17:36
was damaged - 0.1%
AI
Bristol turret
18:17:48
was damaged - 0.1%
AI
Bristol turret
18:18:26
damaged - 0.4%
Noraj
Bristol F2B (F.III)
18:18:26
damaged - 0.4%
Noraj
Bristol F2B (F.III)
18:18:56
was damaged - 0.1%
AI
Bristol turret
18:18:56
was damaged - 0.1%
AI
Bristol turret
18:18:58
was damaged - 0.7%
AI
Bristol turret
18:18:58
was damaged - 0.1%
AI
Bristol turret
18:18:58
was damaged - 0.7%
AI
Bristol turret
18:18:58
was damaged - 0.1%
AI
Bristol turret
18:18:59
was damaged - 0.2%
AI
Bristol turret
18:19:16
damaged - 0.1%
Noraj
Bristol F2B (F.III)
18:19:24
damaged - 0.3%
Noraj
Bristol F2B (F.III)
18:19:28
was damaged - 0.1%
AI
Bristol turret
18:19:30
was damaged - 0.6%
AI
Bristol turret
18:19:30
was damaged - 0.1%
AI
Bristol turret
18:19:59
damaged - 0.8%
Noraj
Bristol F2B (F.III)
18:19:59
wounded - 48.4%
AI
Aircraft gunner
18:19:59
damaged - 0.1%
Noraj
Bristol F2B (F.III)
18:19:59
wounded - 28.6%
AI
Aircraft gunner
18:20:02
was damaged - 0.7%
AI
Bristol turret
18:20:02
was damaged - 0.1%
AI
Bristol turret
18:20:02
was damaged - 0.3%
AI
Bristol turret
18:20:31
damaged - 0.2%
Noraj
Bristol F2B (F.III)
18:20:33
wounded - 23.0%
AI
Aircraft gunner
18:20:33
KILLED
AI
Aircraft gunner
18:20:38
damaged - 0.2%
Noraj
Bristol F2B (F.III)
18:20:38
damaged - 0.2%
Noraj
Bristol F2B (F.III)
18:20:44
damaged - 4.7%
Noraj
Bristol F2B (F.III)
18:20:44
damaged - 2.8%
Noraj
Bristol F2B (F.III)
18:20:44
damaged - 0.3%
Noraj
Bristol F2B (F.III)
18:20:44
damage - 2.5%
18:20:44
damage - 2.3%
18:20:44
damage - 0.3%
18:20:45
damage - 0.2%
18:20:46
damage - 0.1%
18:20:47
damage - 0.7%
18:20:47
damage - 0.1%
18:21:07
damage - 4.9%
18:21:07
damage - 42.9%
18:21:07
damage - 0.1%
18:25:08
SHOTDOWN
Noraj
Bristol F2B (F.III)
* 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.