37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1434232 |
Time | |
Date | 201703 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZAB.ARTCC |
State Reference | NM |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport High Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 119 |
Flight Phase | Cruise |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 200 Flight Crew Total 850 Flight Crew Type 200 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
While conducting skydiving operations; I placed a two-minute call to ZAB center per the letter of agreement (LOA) between ZAB and the skydive operator. Center then called traffic seven miles out. He advised it was fast moving; but did not specify a speed or an ETA.per the LOA; I was supposed to call the traffic as either 'in sight' or 'no factor' before releasing the jumpers. Not having the traffic in sight; but believing it was far enough away as to not be a factor; I released the jumpers and inadvertently omitted the 'no factor' call to center. The traffic passed close enough to the jumpers to cause the ZAB controller some concern. Typically; traffic that is seven miles out will not be a factor at the two minute mark. However; this traffic was fast moving and I failed to take that into account in making my determination. Contributing to this was my inexperience as a skydive pilot. As of the date of this incident; I had been working in the position less than three months. This was my first day conducting skydive operations away from the airport where I usually work.
Original NASA ASRS Text
Title: Sky dive pilot reported releasing jumpers without proper coordination with ATC; resulting in reduced separation between jumpers and other traffic.
Narrative: While conducting skydiving operations; I placed a two-minute call to ZAB center per the Letter of Agreement (LOA) between ZAB and the skydive operator. Center then called traffic seven miles out. He advised it was fast moving; but did not specify a speed or an ETA.Per the LOA; I was supposed to call the traffic as either 'in sight' or 'no factor' before releasing the jumpers. Not having the traffic in sight; but believing it was far enough away as to not be a factor; I released the jumpers and inadvertently omitted the 'no factor' call to Center. The traffic passed close enough to the jumpers to cause the ZAB controller some concern. Typically; traffic that is seven miles out will not be a factor at the two minute mark. However; this traffic was fast moving and I failed to take that into account in making my determination. Contributing to this was my inexperience as a skydive pilot. As of the date of this incident; I had been working in the position less than three months. This was my first day conducting skydive operations away from the airport where I usually work.
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.