The 3D radar has a new air contact. There are no changes to ESM readings.

turn_1412_blue.txt

turn_1412_blue_intl.txt

1412?

I think it's accurate-- we do appear to have moved quite a bit. I'm a bit surprised the aircraft-- at least the presumed F-4E-- has that kind of loiter endurance. Maybe drop tanks?

 

H018 gets the standard ID requests and warnings. I can't anticipate any other changes to our plans until new data or closer approach-- assuming no answer or answer identifying as Iranian and continued approach, classify hostile; final warning at 25 nm; fire at 13 nm.

 

On a tech note: although all earlier turn files could be opened with no difficulty, this one throws an unhandled exception error: "Add failed. Duplicate key value supplied." I have copy-pasted the Details section below. If I hit Continue, it seems to load fine and, at least as near as I can tell, all the relevant data is displayed, though if I then try to load another turn file, it fails.

 

 

 

Details:

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Add failed. Duplicate key value supplied.
at Microsoft.VisualBasic.Collection.Add(Object Item, String Key, Object Before, Object After)
at SimPlot_Viewer.FileLoad.LoadBearings(String[] textline)
at SimPlot_Viewer.FileLoad.Load(String path)
at SimPlot_Viewer.Form1.MenuLoad_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
SimPlot Viewer
Assembly Version: 0.9.1.0
Win32 Version: 0.9.1.0
CodeBase: file:///C:/Users/yisht/Desktop/SimPlot%20Viewer/SimPlot%20Viewer.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1586.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I think it's accurate-- we do appear to have moved quite a bit. I'm a bit surprised the aircraft-- at least the presumed F-4E-- has that kind of loiter endurance. Maybe drop tanks?

I am thinking this F-4E was not configured for attack, reinforcing the theory that it was gunning for the Hormone B.

 

I experienced the same exception error with the turn file.

I will look at the files when I get home from work tonight.

 

The game advanced to 1412 due to standing orders on both sides. This way, the game will not drag on for months.

The game advanced to 1412 due to standing orders on both sides. This way, the game will not drag on for months.

 

Good plan.

I uploaded corrected turn files. Please download them again. The problem is that in SimPlot the ESM bearing lines do not get updated unless they are displayed. I will have to correct that.

Ah. Yes, no problems now.

 

I'll stick with my previously stated plans.

Yishten, what do you make of this helo contact? Shore based AH-1J SeaCobra? Bell 214?

Based on the speed, if I had to guess I'd say an AB-204 off an ex-Sumner. Second guess would be an AB-212 or maybe the SeaCobra. I favor the ABs because my gut says it's here to keep tabs on us and rotate out the P3-F rather than make an attack run, though of course those aren't mutually exclusive options.

It's going slower than I'd have expected from a 214.

Based on the speed, if I had to guess I'd say an AB-204 off an ex-Sumner. Second guess would be an AB-212 or maybe the SeaCobra. I favor the ABs because my gut says it's here to keep tabs on us and rotate out the P3-F rather than make an attack run, though of course those aren't mutually exclusive options. It's going slower than I'd have expected from a 214.

 

I hope it is an AB204 off a Babr (Sumner). It is a wasted asset, imho. The P-3F already has us under observation, and has superior endurance to anything the helo might offer.