Talk:Joint precision approach and landing system

I began this page, using LAAS as a template. JPALS is a military extension of LAAS technology, modified for military use.

I would appreciate it if someone would create a JPALS thumbnail and picture to the right, using one of the pics on Stanford's JPALS website (link is at the bottom). The best pic would be a screen snapshot of the JPALS system hierarchy - however, there may be copyright issues, in which case keeping the LAAS picture is fine, as the military system operates in much the same way. Dr1819 15:35, 13 April 2006 (UTC)


 * I began a very rough draft for JPALS, but never got around to finishing it. If you see anything worth adding from there, go ahead and take it. I made it along with the LAAS page at the same time, so they were very similar. --Dual Freq 22:46, 13 April 2006 (UTC)


 * Minor edit reordering the See Also in order of relevance to the topic. I'm considering deleting the reference to differential GPS.  While it was a start, it's fallen by the wayside, even though WAAS remains technically a form of differential GPS.  What say you others?  Dr1819 23:36, 13 June 2006 (UTC)

Is it really true that JPALS is a "spinoff" from LAAS? I thought it was developed independantly? Maury 15:13, 14 June 2006 (UTC)

No - LAAS work began before JPALS was little more than a concept. JPALS incorporates most of the LAAS technology, with some key additions that provide authentication, encryption, and anti-jam measures. These measures prevent unauthorized use, deter hijacking of the signal, and guard against signal degredation by enemy means. Both systems were developed simultaneously, with significant overlap. There's not a lot of unclassified information available right now, but it appears that JPALS units installed aboard military aircraft will be able to use LAAS signals, as well as the more robust JPALS signals. Any other possibility, to put it bluntly, doesn't pass the sanity test, particularly given the FAA's emphasis towards phasing out non-WAAS/LAAS systems for all but the most heavily trafficked airfields. In fact, there's been considerable talk about authorizing handheld units for instrument approaches, provided they meet certain RAIM requirements, as well as the current requirements governing IAP database currency, airfield and approach selection procedures, etc. This would bust cheap instrument approach procedures wide open, with a sub-$500 handheld being able to provide equivalent accuracy in a WAAS environment, and better than CAT-IIIc accuracy in an LAAS environment. Expect to see new FAA regs governing the programmed display options, to ensure adherency to generally accepted standards.

Edited for grammer. —The preceding unsigned comment was added by Special:Contributions/ (talk)

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on Joint Precision Approach and Landing System. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Corrected formatting/usage for http://gps.faa.gov/Library/laas-f-text.htm
 * Added archive https://web.archive.org/web/20060311054600/http://www.raytheon.com/products/jpals/ to http://www.raytheon.com/products/jpals/
 * Added archive https://web.archive.org/web/20140911053740/http://www.navair.navy.mil/index.cfm?fuseaction=home.displayPlatform&key=8559E3E9-42F1-4A08-876B-5F2E7FA6AAB2 to http://www.navair.navy.mil/index.cfm?fuseaction=home.displayPlatform&key=8559E3E9-42F1-4A08-876B-5F2E7FA6AAB2
 * Added archive https://web.archive.org/web/20140911052320/http://www.navair.navy.mil/index.cfm?fuseaction=home.PhotoGalleryDetail&key=62593B59-C3A0-454F-8CA4-594D953A0005 to http://www.navair.navy.mil/index.cfm?fuseaction=home.PhotoGalleryDetail&key=62593B59-C3A0-454F-8CA4-594D953A0005

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 13:34, 26 April 2017 (UTC)