Normalchecklist

Update: Never mind, I ran the updater from the utilities menu inside P2A and it worked fine. I now current. Interesting, I thought this was already fixed and I haven’t run into any conflict while importing the plan from Simbrief. But P2A is indeed showing AIRAC 2413, while the Navigraph tool shows that P2A is current. I guess P2A doesn’t care about the AIRAC version while importing plan from a Simbrief.

It is not AI. I like P2A much better than Say Intentions.

This was with 0.1.3 I get multiple back to back instruction by Approach, which is difficult to memorize. at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource) at System.Collections.Generic.List`1.Enumerator.MoveNextRare() at P2ADataLinq.FlightStateMgr.CheckActiveTriggers() 2025-04-20 11:41:35.0429|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 0 in UnInterruptAudio 2025-04-20 11:41:35.0429|INFO|A.c0a0e4f0f922705579dcca7063389a951|Copilot Speaks Response: ~ Descend via the GUERA two arrival with the GUERA transition to seven thousand feet . Altimeter three zero zero niner DELTA Seven Three Niner 2025-04-20 11:41:35.0429|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 1 in InterruptAudio 2025-04-20 11:41:35.0429|INFO|P2ADataLinq.Speech.SpeechMgr| WaveOutPlayer Paused in InterruptAudio 2025-04-20 11:41:35.0429|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter Paused in SpeakPhrase 2025-04-20 11:41:35.7732|INFO|A.c0a0e4f0f922705579dcca7063389a951|Processing Exchange Complete:ProcessActiveExchange-CopilotResponded 2025-04-20 11:41:35.7732|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter UnPaused in OnTTSWavePlaybackStopped 2025-04-20 11:41:46.1427|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 0 in UnInterruptAudio 2025-04-20 11:41:46.1647|INFO|P2ADataLinq.ATCListener|Initial Recognized Speech: Descend via the GUERA2 arrival with the GUERA transition to Seven Thousand Feet Altimeter Three Zero Zero Niner DELTA Seven Three Niner 2025-04-20 11:41:46.1647|INFO|P2ADataLinq.ATCListener|Handled Recognized Speech: Descend via the GUERA2 arrival with the GUERA transition to Seven Thousand Feet Altimeter Three Zero Zero Niner DELTA Seven Three Niner 2025-04-20 11:41:46.1647|INFO|P2ADataLinq.Controller|HandleSTARReadback 2025-04-20 11:41:46.1647|INFO|A.c0a0e4f0f922705579dcca7063389a951|Chatter UnPaused in OnTTSResponseSpeechEnded 2025-04-20 11:41:46.1647|INFO|A.c0a0e4f0f922705579dcca7063389a951|Processing Exchange Complete:OnTTSResponseSpeechEnded - Response Ended 2025-04-20 11:41:46.1647|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter UnPaused in OnTTSWavePlaybackStopped 2025-04-20 11:41:46.6491|INFO|A.c0a0e4f0f922705579dcca7063389a951|ATC Speaks: DELTA Seven Three Niner turn left to heading one eight zero descend and maintain four thousand feet You are Twenty tree nautical miles East of the airport. fly heading two two zero to intercept final. descend and maintain tree thousand tree hundred feet Cleared for RNAV Yankee approach to runway Two Six . Contact Camarillo Tower on one two eight point two 2025-04-20 11:41:46.6491|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 1 in InterruptAudio 2025-04-20 11:41:46.6491|INFO|P2ADataLinq.Speech.SpeechMgr| WaveOutPlayer Paused in InterruptAudio 2025-04-20 11:41:46.6491|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter Paused in SpeakPhrase 2025-04-20 11:41:48.1890|INFO|P2ADataLinq.ChatterMgr|Approach ChatterFolder: C:\Pilot2ATC_3_x64\Sounds\ATC_Chatter\Regions\United States\Controllers\App 2025-04-20 11:41:48.1895|INFO|P2ADataLinq.ChatterMgr|Approach ChatterFolder: C:\Pilot2ATC_3_x64\Sounds\ATC_Chatter\Regions\United States\Controllers\App 2025-04-20 11:42:10.5727|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 0 in UnInterruptAudio 2025-04-20 11:42:10.5727|INFO|A.c0a0e4f0f922705579dcca7063389a951|Copilot Speaks Response: ~ turn left to heading one eight zero descend and maintain four thousand feet Fly heading two two zero descend and maintain tree thousand tree hundred feet Cleared for RNAV Yankee approach to runway Two Six . Tower on one two eight point two , DELTA Seven Three Niner 2025-04-20 11:42:10.5727|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 1 in InterruptAudio 2025-04-20 11:42:10.5727|INFO|P2ADataLinq.Speech.SpeechMgr| WaveOutPlayer Paused in InterruptAudio 2025-04-20 11:42:10.5727|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter Paused in SpeakPhrase 2025-04-20 11:42:11.3339|INFO|A.c0a0e4f0f922705579dcca7063389a951|Processing Exchange Complete:ProcessActiveExchange-CopilotResponded 2025-04-20 11:42:11.3339|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter UnPaused in OnTTSWavePlaybackStopped 2025-04-20 11:42:13.3619|INFO|P2ADataLinq.ChatterMgr|Approach ChatterFolder: C:\Pilot2ATC_3_x64\Sounds\ATC_Chatter\Regions\United States\Controllers\App 2025-04-20 11:42:13.4790|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: I 2025-04-20 11:42:13.4790|INFO|P2ADataLinq.Data.FltPlan|NextWpt: GUERA 2025-04-20 11:42:18.7728|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E2 2025-04-20 11:42:18.7728|INFO|P2ADataLinq.Data.FltPlan|NextWpt: SESPE 2025-04-20 11:42:18.7728|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E2 2025-04-20 11:42:18.7728|INFO|P2ADataLinq.Data.FltPlan|NextWpt: SESPE

I think you will be fine as long as your plane and P2A have the same navigation charts version.

I have not used FS2Crew in ages. Is there an option for pushing a button to talk to FS2Crew? That would prevent interference since you talk to ATC while pushing the Push to Talk button.

Hi Dave, I confirm it will be an issue with this plane. The trick doesn’t work because the audio panel of the MD80 doesn’t have pushbuttons for the audio of each channel. It only has volume sliders and there is no way to turn a channel off. The MIC buttons had no effect on P2A either.

Dave,There is an issue in version 29 where Center is repeating back to back the descend clearance (see log below). Notice there are clearances to 2 different altitudes 14000 then 13000. “UNITED Seven Three Niner Descend via the ANJLL4 arrival with the SHTNR transition to fourteen thousand feet Altimeter three zero one niner at Los Angeles International Airport Descend via the ANJLL four arrival with the SHTNR transition thirteen thousand feet for the ILS approach to runway Two Five left with the CRCUS transition at Los Angeles International Airport” If I read back one half of this instruction then P2A doesn’t understand and stops responding. I replicated this 3 times. On the 3rd flight I decided to report again to Center “Callsign at 13000” and Center finally transferred me to Approach. Also, I didn’t get the “expect ANJLL4 arrival” in any of the flights. The route was KLAS RADYR2 BLAQQ SHTNR ANJLL4 KLAX This a the fragment of the log before it was awry: 2025-01-10 21:21:00.8404|INFO|P2ADataLinq.ATCListener|Handled Recognized Speech: Center UNITED Seven Three Niner Climbing to Flight Level Two Eight Zero 2025-01-10 21:21:00.8404|INFO|P2ADataLinq.Controller|HandleInitialContact 2025-01-10 21:21:00.8404|INFO|P2ADataLinq.Data.SpeechGenerator|SpokenRandomGreeting Hour: 8 2025-01-10 21:21:00.8404|INFO|P2ADataLinq.Data.SpeechGenerator|SpokenRandomGreeting Hour: 8 2025-01-10 21:21:00.8490|INFO|P2ADataLinq.Controller|HandleInitialCenterContact 2025-01-10 21:21:00.9113|INFO|P2ADataLinq.Controller|SpeakAltimeterSetting 2025-01-10 21:21:00.9298|INFO|P2ADataLinq.Controller|CheckSquawkCode 2025-01-10 21:21:01.1200|INFO|A.c0a0e4f0f922705579dcca7063389a951|ATC Speaks: UNITED Seven Three Niner goodday . 2025-01-10 21:21:01.1200|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 1 in InterruptAudio 2025-01-10 21:21:01.1200|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter Paused in SpeakPhrase 2025-01-10 21:21:05.0332|INFO|P2ADataLinq.Speech.SpeechMgr|AudioInterrupts: 0 in UnInterruptAudio 2025-01-10 21:21:05.0332|INFO|A.c0a0e4f0f922705579dcca7063389a951|Chatter UnPaused in OnTTSSpeechEnded 2025-01-10 21:21:05.0332|INFO|A.c0a0e4f0f922705579dcca7063389a951|Processing Exchange Complete:OnTTSSpeechEnded - No Response 2025-01-10 21:21:05.0332|INFO|P2ADataLinq.Speech.SpeechMgr|Chatter UnPaused in OnTTSWavePlaybackStopped 2025-01-10 21:21:34.4312|INFO|P2ADataLinq.Controller|RespondToFlightTrigger: ReachedNextFltPlanWaypoint 2025-01-10 21:21:34.4312|INFO|P2ADataLinq.Controller|RespondToFlightTriggerValidated Trigger:ReachedNextFltPlanWaypoint 2025-01-10 21:21:34.4312|INFO|P2ADataLinq.Controller|rOnReachedNextFltPlanWaypoint: RADYR; 9:21:34 PM 2025-01-10 21:21:41.4709|INFO|P2ADataLinq.Data.FltPlan|SetNearestActiveWaypoint: BLAQQ 2025-01-10 21:21:42.4472|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E1 2025-01-10 21:21:42.4472|INFO|P2ADataLinq.Data.FltPlan|NextWpt: BLAQQ 2025-01-10 21:23:08.0770|INFO|P2ADataLinq.Controller|RespondToFlightTrigger: ReachedNextFltPlanWaypoint 2025-01-10 21:23:08.0770|INFO|P2ADataLinq.Controller|RespondToFlightTriggerValidated Trigger:ReachedNextFltPlanWaypoint 2025-01-10 21:23:08.0770|INFO|P2ADataLinq.Controller|rOnReachedNextFltPlanWaypoint: BLAQQ; 9:23:08 PM 2025-01-10 21:23:16.0770|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E2 2025-01-10 21:23:16.0770|INFO|P2ADataLinq.Data.FltPlan|NextWpt: SHTNR 2025-01-10 21:23:16.0770|INFO|P2ADataLinq.Data.FltPlan|CheckNextWaypoint: E2 2025-01-10 21:23:16.0770|INFO|P2ADataLinq.Data.FltPlan|NextWpt: SHTNR 2025-01-10 21:23:41.3165|INFO|P2ADataLinq.AsyncTCPClient|Socket connected to 127.0.0.1:48007 2025-01-10 21:25:12.9426|INFO|P2ADataLinq.Controller|RespondToFlightTrigger: ReachedFirstSTARWaypoint 2025-01-10 21:25:12.9426|INFO|P2ADataLinq.Controller|RespondToFlightTriggerValidated Trigger:ReachedFirstSTARWaypoint 2025-01-10 21:25:12.9426|INFO|P2ADataLinq.Controller|rOnFirstSTARWaypointReached 2025-01-10 21:25:12.9740|INFO|P2ADataLinq.FlightStateMgr|State Changed to: STARDescent 2025-01-10 21:25:13.0112|INFO|P2ADataLinq.Controller|SpeakAltimeterSetting 2025-01-10 21:25:15.3634|INFO|P2ADataLinq.WxMgr|Retrieving weather from web successful at 1/10/2025 9:25:15 PM 2025-01-10 21:25:15.3634|INFO|P2ADataLinq.Controller|ReachedArrivalSetup triggered in onFirstSTARWaypointReached. 2025-01-10 21:25:15.3814|INFO|P2ADataLinq.Controller|rOnReachedArrivalSetup 2025-01-10 21:25:15.3814|INFO|P2ADataLinq.Controller|SetUpIFRArrival:KLAX 2025-01-10 21:25:20.8693|INFO|P2ADataLinq.ATCListener|AddUserNames Succeeded 2025-01-10 21:25:20.8693|INFO|P2ADataLinq.ATCMgr|AssignedAPPR: ILS RW25L - 2025-01-10 21:25:20.8693|INFO|P2ADataLinq.ATCMgr|AssignedRunway: RW25L - 2025-01-10 21:25:20.8693|INFO|P2ADataLinq.ATCMgr|AssignedSTAR: ANJLL4 - 2025-01-10 21:25:20.8693|INFO|P2ADataLinq.Controller| ATC FlightPlan Changed 2025-01-10 21:25:20.9098|ERROR|P2ADataLinq.FlightStateMgr|Error checking trigger: ReachedFirstSTARWaypoint : System.InvalidOperationException: Collection was modified; enumeration operation may not execute. at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource) at System.Collections.Generic.List`1.Enumerator.MoveNextRare() at P2ADataLinq.FlightStateMgr.CheckActiveTriggers() 2025-01-10 21:25:21.9014|INFO|A.c0a0e4f0f922705579dcca7063389a951|ATC Speaks: UNITED Seven Three Niner Descend via the ANJLL4 arrival with the SHTNR transition to fourteen thousand feet Altimeter three zero one niner at Los Angeles International Airport Descend via the ANJLL four arrival with the SHTNR transition thirteen thousand feet for the ILS approach to runway Two Five left with the CRCUS transition at Los Angeles International Airport

Yeah, there is something broken in 29. I did the same route KLAS RADYR2 MISEN ANJLL4 KLAX twice and saw similar behavior. Center told me to descend via ANJLL4 arrival to 14000, interestingly in both flight it gave me this instruction twice back to back. Then forgot about me, and never transferred me to Approach.

The other day I tried letting P2A assign the approach and now I have a question. I was arriving via ANJLL4 to RWY 25L in KLAX and was assigned ILS 25L but without a transition. ILS 25L has 5 different IAFs. Once I got to the last waypoint of the ANJLL4 arrival which happens to be CRCUS I was given a direct to HUNDA. This was unusual since I could have joined the ILS at CRCUS. I verbally requested the CRCUS transition but P2A didn’t understand. So I went to set the request via the P2A menu so that P2A would verbally request the approach, but there is no option to add an approach transition to the request. Are approach transitions not implemented in P2A verbal requests? At the end I uploaded and activated the approach via the procedures button and P2A worked fine.

The issue is that Zibo loads with both Coms ON. Seems this is confusing P2A. If you turn Com2 OFF from your aircraft radio panel, then P2A interface populates the Coms.

I had the same experience, but it fixed itself after rebooting the PC. Initially restarting XP12 and P2A did not help.

@Divij well I figured something out for x-plane, I don’t have MSFS. But something similar might exist for it. I edited file "X-Plane 12\Resources\vr\interaction_profiles\reverb_g2_controller.json" by deleting this section. Notice there are two instances of this inside the file, one for each controller right/left. { "path": "output/haptic", "type": "haptic" }

@Divij did you find a way to disable haptics?

I was on the climb via the SID and was handed off to another Center. And just when I was swapping to the new assigned frequency I got additional climb instructions that I cut off. Is this a bug? I don’t expect a station talking to me again after handing me off to another station.

It happens to me sometimes, but I haven’t figured how to replicate it. Sometimes restarting P2A fixes it, and sometimes you have to click on P2A the COM button where it should say com1.