VFR RESTRICTION GIVEN BY CTLR IN ERROR WHILE FLT WAS IN IMC.

1988-05 · NASA ASRS report 87124

Date: 1988-05 · Aircraft: Small Transport

Anomalies: inflight-event-encounter-weather-turbulence|other-no-specific-anomaly-occurred|other-unspecified

Synopsis

VFR RESTRICTION GIVEN BY CTLR IN ERROR WHILE FLT WAS IN IMC.

Narrative

WE ASKED FOR AN IFR CLRNC FOR THE ILS INTO SAN JOSE. OAKLAND CENTER CLRED US TO DESCEND TO 8000' ON A 360 HEADING. WE ADVISED THAT IN ORDER TO COMPLY WE WOULD HAVE TO HAVE A CLRNC SOON. WE WERE THEN CLRED TO SAN JOSE; RADAR VECTORS FOR THE ILS; ASKED FOR A GOOD RATE OF DESCENT (WE GAVE 3500'/MIN) AND AN INTERCEPT FOR THE ILS. WE WERE THEN CLRED AND AN INTERCEPT FOR THE ILS. WE WERE THEN CLRED TO INTERCEPT THE LOC AND MAINTAIN 8000' AND HANDED OFF TO BAY APCH ON 120.1. OUR SPEED AT THIS POINT WAS 240 KTS INDICATED. ON HANDOFF WE WERE TOLD TO TURN RIGHT OT 360 DEG; DESCEND TO 4000' AND REMAIN VFR. AT THIS POINT WE FLEW INTO SOLID IMC WHICH WE REPORTED. THE CTLR SOUNDED REALLY TENSE; FOR THE REMAINDER OF AN UNEVENTFUL ILS TO SAN JOSE. PROBLEM: WE HAD AN IFR CLRNC FROM CENTER BUT BAY APPEARED TO HAVE NO KNOWLEDGE OF IT AND ISSUED VECTORS WHICH PUT US IN IMC BEFORE THE 'REMAIN VFR' PART OF HIS CLRNC. TO OUR KNOWLEDGE NO HAZARD WAS CAUSED BUT THE POTENTIAL DOES EXIST AND CAUSES SOME CONCERN ON OUR PART. ESPECIALLY IN LIGHT OF THE OBVIOUS EFFECT ON THE CTLR. THE HANDLING WAS AS THOUGH WE WERE STUDENT PLTS. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING INFORMATION: RPTR FOUND OUT WHEN HE CALLED THE TRACON THAT THE INCIDENT OCCURRED BECAUSE OF A 'PAPERWORK' PROBLEM IN THE TRACON. WHEN RPTR WAS INBOUND TO SJC AS A VFR FLT RECEIVING ADVISORIES FROM THE CENTER; THIS GENERATED A FLT PROGRESS STRIP AT THE APCH CTLR POS THAT SHOWED THE FLT TO BE VFR. WHEN RPTR FILED IFR ABOUT EIGHTY MILES FROM DEST; ANOTHER FLT PROGRESS STRIP WAS GENERATED SHOWING THE FLT TO BE IFR. BOTH STRIPS WERE AT THE APPROPRIATE POS IN THE TRACON. THE CTLR PICKED UP THE WRONG STRIP DURING THE HANDOFF; AND THOUGHT THE ACFT WAS VFR. WITH THE HIGH SPEED OF RPTR'S ACFT; THE CTLR'S FIRST THOUGHT WAS TO VECTOR FOR SPACING OFF THE LOC. THE VFR RESTRICTION GIVEN TO RPTR WAS GIVEN BECAUSE CTLR THOUGHT THE FLT WAS VFR. NO LOSS OF SEP OCCURRED AND RPTR'S ACFT DID NOT GET LOW ENOUGH TO CAUSE TERRAIN CONFLICT. AS SOON AS RPTR TOLD CTLR HE WAS IN CLDS; CTLR THOUGHT PLT HAD ENTERED CLDS WITHOUT CLRNC. THIS WAS THE REASON RPTR WAS ASKED TO CALL TRACON AFTER LNDG.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.