37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1365072 |
Time | |
Date | 201606 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZOA.ARTCC |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Sail Plane |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Glider Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 80 Flight Crew Total 5000 Flight Crew Type 45 |
Person 2 | |
Function | Pilot Flying |
Qualification | Flight Crew Glider Flight Crew Private Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 120 Flight Crew Total 1750 Flight Crew Type 1150 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Inflight Event / Encounter Weather / Turbulence |
Narrative:
We were flying mountain wave conditions [along the eastern sierra nevada]. We had prearranged a clearance for operations inside R-2508 in class a airspace. The weather conditions had been hugely favorable [for several hours]. We had to work to remain below class a airspace. We had worked successfully on two clearances with oakland already on this day. The first oakland clearance was approximately an hour in the morning and the second clearance was 90 minutes in the afternoon.on our next leg southbound; we asked oak for another clearance. They were very cooperative; and gave us a block altitude assignment; FL170 to FL230. The frequency was busy with traffic at this time. We encountered a loss of lift; and could not reestablish a positive climb rate. We asked for a lower clearance and were told MEA was 14;500 MSL for terrain separation; 'could we ensure terrain separation?' yes; we replied. We heard another aircraft diverted around us for separation. We tried to ask and confirm our lower block assignment and couldn't contact oak. We tried to cancel IFR and couldn't contact oak. Oak continued to try to confirm us to cancel and another aircraft confirmed to oak that we were hearing their calls; answering and trying to cancel our clearance. We had to turn northbound to retain glide to a runway; given the rate of sinking air mass. The relay pilot confirmed to oak that we wished to cancel IFR. The problem occurred partially because we anticipated a similar air mass to our two prior passes through the area on this day. Secondly; we didn't anticipate a loss of radio contact at 14;500 MSL; nor a great density of IFR traffic in the region to create a 'near miss' situation. The congestion on the frequency contributed to the delay in our request to cancel IFR. We have no idea how close the [other aircraft] was to us; we never saw that aircraft.how do we prevent this in the future?for ATC; for gliders to not authorize a lower floor of block assignment; to come near to the floor of radio coverage in the sector. For me as a pilot; to not request a block clearance unless we are established in extremely strong lifting conditions; and can maintain more than 1000 ft above our floor of the block. We should cancel immediately; if the trend is penetrating the interior buffer on our floor.
Original NASA ASRS Text
Title: Sailplane instructor and student reported lifting conditions diminished greatly and the pilots were unable to maintain their block assignment or contact ATC directly. The pilots turned back toward the departure airport before ATC clearance could be received.
Narrative: We were flying mountain wave conditions [along the eastern Sierra Nevada]. We had prearranged a clearance for operations inside R-2508 in Class A airspace. The weather conditions had been hugely favorable [for several hours]. We had to work to remain below class A airspace. We had worked successfully on two clearances with Oakland already on this day. The first Oakland clearance was approximately an hour in the morning and the second clearance was 90 minutes in the afternoon.On our next leg southbound; we asked OAK for another clearance. They were very cooperative; and gave us a block altitude assignment; FL170 to FL230. The frequency was busy with traffic at this time. We encountered a loss of lift; and could not reestablish a positive climb rate. We asked for a lower clearance and were told MEA was 14;500 MSL for terrain separation; 'Could we ensure terrain separation?' Yes; we replied. We heard another aircraft diverted around us for separation. We tried to ask and confirm our lower block assignment and couldn't contact OAK. We tried to cancel IFR and couldn't contact OAK. OAK continued to try to confirm us to cancel and another aircraft confirmed to OAK that we were hearing their calls; answering and trying to cancel our clearance. We had to turn northbound to retain glide to a runway; given the rate of sinking air mass. The relay pilot confirmed to OAK that we wished to cancel IFR. The problem occurred partially because we anticipated a similar air mass to our two prior passes through the area on this day. Secondly; we didn't anticipate a loss of radio contact at 14;500 MSL; nor a great density of IFR traffic in the region to create a 'near miss' situation. The congestion on the frequency contributed to the delay in our request to cancel IFR. We have no idea how close the [other aircraft] was to us; we never saw that aircraft.How do we prevent this in the future?For ATC; for gliders to not authorize a lower floor of block assignment; to come near to the floor of radio coverage in the sector. For me as a pilot; to not request a block clearance unless we are established in extremely strong lifting conditions; and can maintain more than 1000 ft above our floor of the block. We should cancel immediately; if the trend is penetrating the interior buffer on our floor.
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.