TARP?

ZapBrannigan

If it ain’t a Boeing, I’m not going. No choice.
Could someone talk about the Terminal Analysis and Review Program and explain it in laymans terms? Also, could you say if this system is now operational at all TRACONS? And finally, what triggers automated reporting?

Thanks!
 
Could someone talk about the Terminal Analysis and Review Program and explain it in laymans terms? Also, could you say if this system is now operational at all TRACONS? And finally, what triggers automated reporting?

Thanks!

It's a "snitch patch." I am not sure where it is operational, when it's turned on (IE, is it running 24/7), or what block of time is audited (X amount of time per day, or every event, etc) system wide. It's deployment and use, however, are not the same at every facility last time I heard - and has been ever changing, partly due to the drastic change of our reporting/processing of errors as of late. All I know are those parameters at my own facility.

It measures standard radar separation (to include wake) to the hundredth of a mile.
 
This is all i could turn up after searching google:

From a Major Airline Safety Committee.


Terminal Analysis and Review Program (TARP) Cautions

There have been some significant changes made concerning how air traffic control (ATC) reports and processes pilot deviations (PD). In the past, if a controller observed or was alerted to a clearance deviation, he or she had some latitude in the decision about whether or not to file a PD. Generally speaking, if there was no loss of separation, controllers often chose to send our crews on with a reassuring "no problem" and did not report the deviation.

In January 2012, this level of discretion was curtailed in DFW with the introduction of the Terminal Analysis and Review Program (TARP), an automatic system that monitors pre-established separation parameters and generates alerts when an aircraft approaches the limits of these parameters. Each TARP alert creates an Electronic Occurrence Report (EOR) that is forwarded to an ATO Service Area Safety Office for review. Committees at these safety offices review each EOR and decide if a PD will be filed. Due to the automation involved, deviations can result without the local ATC’s knowledge. Since TARP began, there have been at least three PDs filed without our crews having received any indication from ATC.

At the same time TARP was deployed, a PD reporting program for ATC was rolled out by the Federal Aviation Administration. The new program reflects the FAA’s recent emphasis on the use of voluntary disclosure programs (such as the Aviation Safety Action Program) to enhance safety. Controllers are now required to report any safety of flight occurrence they observe through the use of Mandatory Occurrence Reports (MOR). Much like EORs, MORs are forwarded to the Service Area Safety Offices for review.

If a controller believes that a deviation did not jeopardize the safety of a flight, they have another option that satisfies the FAA’s reporting requirements. Instead of filing an MOR, the controller can submit an Air Traffic Safety Action Program (ATSAP) report. ATSAP is a voluntary disclosure program for controllers that is governed by the same immunity and confidentiality provisions of our ASAP memorandum of understanding. The American Airlines ASAP program recently signed an information-sharing agreement with ATSAP, and through a secure portal we now have access to ATSAP reports that involve AA aircraft in any way. In some cases, these reports have alerted APA and, in turn, our crews of potential pilot deviations.

We work closely with ATC and share the common goal of getting our passengers to their destinations safely. In light of these recent changes, however, we strongly encourage all pilots to file ASAP reports whenever anything that could possibly be categorized as a violation occurs, no matter what your controller may say to the contrary.
 
To supplement what cmill posted, the article suggests that the TARP was "turned on" in January of 2012. That is not true. What happened in 2012 was a change to whom the TARP reports were sent to, and how they are processed.

Prior to that, all the variables that I mentioned in my first reply came into play...and some of them are still in play.

Between these replies I asked two buddies that work at two different facilities that provide radar service. TARP is not on at either for the time being.
 
What about altitude busts? Does it automatically report those as well?

Not unless it results in a loss of separation. It's a formula, it has no idea what you've been told (visual, altitude, etc). It reads mode C and target position, then calculates...
 
To add a little. When we received TARP it was to be reviewed 2 hours a month. That later changed to 24/7. Any loss of standard separation is forwarded off site for potential review. I believe sub 70% is the mandatory review threshold. TARP also processes not to the hundredth of a mile as Tripsix said, but to the thousandth of a mile. Bear in mind ANY action can be observed during these reviews. It need not be limited to the aircraft involved in the loss of standard separation. Just something to keep in mind, say, when arriving to an airport using SIMU visuals to closely spaced runways. Pretty much a constant mandatory review situation.

I don't know to what extent they review the non involved aircraft. I do know I've seen an operational error called on review of a TCAS RA that led to the discovery of two entirely different aircraft that had reported each other in sight, but failed to use the pilot phraseology contained within the .65 7-2-1.

I think probably the biggest change is if you overshoot an altitude by 400 feet with traffic in proximity it will automatically be reviewed and reported. I guess really you wouldn't have to overshoot by your own actions now that I think about it. A valid, but 200 feet high/low readout and a strong updraft/downdraft could be all it takes.
 
ZapBrannigan , not assuming anything, but if you're asking because of a potential issue, I am fairly sure you know about the ASRS program right?
 
i remember the first time that they turned on the TARP at C90 (think it was in 2007 or 2008), it recorded about 100 losses of seperation the first hour. after that they turned it off.
 
Out of curiosity, does TARP report a "low altitude alert" too?
I would think that would be weird. I have gotten several as a result of following a proper non-precision approach profile. Also going into OAK you can get a ton when descending over the hills on all sorts of approaches.



Sent from my Nexus 7 using Tapatalk 2
 
Back
Top