Dave,  on this approach to KFSD, perfect job of comms and vectors until I get the handoff to the tower, where I'm getting no replies. 

Here's the logfile https://drive.google.com/file/d/1ntSOVTbUFdMny6vY0AToQ3vruiyRPMtz/view?usp=sharing 

When I'm saying "American Ninety One inbound on runway zero three"  and similar perturbations, the logfile shows no interpretation.  For me the tower handoff seems to be the most fragile part of P2A.  LOVE this program and much respect for your support.   Some other flexibility would help:    "....established on final for....",  "...on the approach for...." in addition to "...inbound for...."

Started Listening                                                                                      <----- line number 2057
NewGPSWpt: RANOE
NewGPSWpt: RANOE
NewGPSWpt: RANOE
NewGPSWpt: RANOE
UnInterruptAudio in OnPilotEndSpeaking 10/25/2022 22:26:17 
AudioInterrupts: 0 in UnInterruptAudio 22:26:17
Stopped Listening  

There are several phrases that should work:

if you are not yet established on final you can say "American Ninety One inbound for RNAV runway zero three" or substitute other types of approaches for RNAV like ILS or VOR Approach, etc.

If you are on final, you can say "American Ninety One established on final for runway zero three" or "American Ninety One established on final for ILS to runway zero three".

The log file for the flight doesn't even show that a phrase was rejected which leads me to think the program didn't actually hear what you said for some reason.  It shows started and stopped listening, so it is getting the PTT button push and release, but no phrase accepted or rejected.

Try one of the above phrases on the next flight and see what happens.

Dave

Dave, you are a busy man, most grateful.