I feel a lot of apples and oranges discussion going on here. The word vector can refer to many things. If a reference is being made to ORBX Vector then it should have no effect on any area inside an ORBX region. ORBX regions override all ORBX FTX Global files. PANT is clearly inside an ORBX Region.
In reading Steve's posts, it sounds like this problem could have been caused by fsaerodata , a third party package to update the FSX/P3D aeronautical navigational database to current real world data that most of us don't use. This software is mostly used when shooting real world approaches etc. in the sim or if alignment is necessary with a third party air traffic control package like VoxATC etc. If fsaerodata has modified the standard APX12120.bgl file then you may need to put the original file back from a backup. Turning off a standard FSX/P3D APX file to make a scene look right should not be done as unpredictable results may occur. Also, I am a little surprised that a normal APX file would affect elevation.
If the APX file has been corrupted or modified it needs to be replaced from backup with the original to see if that fixes the problem. If the APX12120 file has not been modified by fsaerodata or any other program then the problem clearly lies with an addon elevation file that is affecting the PANT area. It should not be any file that is part of ORBX Global.
If the problem persists with the original APX12120 in place, I recommend you turn off all of your addon sceneries except the PFJ ORBX region, object library and so on(the minimum for ORBX PFJ to run properly) to see if it corrects the elevation.
Rod