 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU center controller reported parachute jump aircraft routinely enter their airspace without any coordination from the TRACON.
| Attributes | |
| ACN | 1465287 |
| Time | |
| Date | 201707 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 119 |
| Flight Phase | Climb |
| Route In Use | VFR Route |
| Flight Plan | VFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Lately this has become an issue. We have been 'blocking' parachute jump airspace over two airports. A few months ago; TRACON started to insist that each and every time a jump aircraft climbed into our airspace; they needed to point him out. These aircraft are VFR and there is no phraseology for a VFR point out. I always just say 'ok' or 'I see him' or 'approved'. This parachute jump activity is under a north departure track so there is frequently vectors to IFR aircraft required to keep these aircraft away.conversely; we 'block' parachute jump airspace on a daily basis with a different TRACON in two places. The duality of this situation bothers me. Someone is right and someone is wrong; so which is it? Can we put a code into the computer; and write an altitude over an airport and block for parachute jump operations or can we not; in which case every time they call with a pointout on an aircraft which we have no data block for; we are required to start a radar track; or put a strip in the bay. Whichever way we decide; it should be the same for both tracons.the TRACON which insists that every single parajump aircraft be pointed out; ran two parajump aircraft through my airspace. Both aircraft went to 14;500 feet well inside my airspace; without coordination; through a busy departure track.
Original NASA ASRS Text
Title: ZAU Center Controller reported parachute jump aircraft routinely enter their airspace without any coordination from the TRACON.
Narrative: Lately this has become an issue. We have been 'blocking' parachute jump airspace over two airports. A few months ago; TRACON started to insist that each and every time a jump aircraft climbed into our airspace; they needed to point him out. These aircraft are VFR and there is no phraseology for a VFR point out. I always just say 'ok' or 'I see him' or 'approved'. This parachute jump activity is under a north departure track so there is frequently vectors to IFR aircraft required to keep these aircraft away.Conversely; we 'block' parachute jump airspace on a daily basis with a different TRACON in two places. The duality of this situation bothers me. Someone is right and someone is wrong; so which is it? Can we put a code into the computer; and write an altitude over an airport and block for parachute jump operations or can we NOT; in which case every time they call with a pointout on an aircraft which we have no data block for; we are required to start a radar track; or put a strip in the bay. Whichever way we decide; it should be the same for both TRACONs.The TRACON which insists that every single Parajump aircraft be pointed out; ran two Parajump aircraft through my airspace. Both aircraft went to 14;500 feet well inside my airspace; without coordination; through a busy departure track.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.