So far I have been unable to use fs2crew with the FSL airbus with out getting a ctd after clicking run preflight events. Any idea what might be causing this?

Never heard of that one before.

So I googled it.

Try this:

https://www.google.com/search?q=fslabs+api.dll&rlz=1C1CHBD_enKR903KR903&oq=fslabs+api.dll&aqs=chrome..69i57.2064j0j7&sourceid=chrome&ie=UTF-8

 

11 hours ago, byork said:

Never heard of that one before.

So I googled it.

Try this:

https://www.google.com/search?q=fslabs+api.dll&rlz=1C1CHBD_enKR903KR903&oq=fslabs+api.dll&aqs=chrome..69i57.2064j0j7&sourceid=chrome&ie=UTF-8

 

Think I fixed it by using the net framework repair tool.

Glad you got it sorted 😉

Looks like I may have spoke too soon. It started happening again shortly after starting FS2crew. I ran test flight without Fs2crew and I did not get this crash. 

Faulting application name: PREPAR3D.EXE, version: 5.1.12.26829, time stamp: 0x5fb44f72
Faulting module name: api.dll, version: 5.1.12.26829, time stamp: 0x5fb4500d
Exception code: 0xc0000005
Fault offset: 0x0000000000022926
Faulting process id: 0x21fc
Faulting application start time: 0x01d71af454357ea8
Faulting application path: C:\Lockheed Martin\Prepar3D v5\PREPAR3D.EXE
Faulting module path: C:\Lockheed Martin\Prepar3D v5\api.dll
Report Id: ff0debbe-f6df-4a23-9572-e53ca71d0e89
Faulting package full name: 
Faulting package-relative application ID: 

Not much I can really say other than try the things listed here:

https://www.google.com/search?q=fslabs+api.dll&rlz=1C1CHBD_enKR903KR903&oq=fslabs+api.dll&aqs=chrome..69i57.2064j0j7&sourceid=chrome&ie=UTF-8