37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 223905 |
Time | |
Date | 199210 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : ptk |
State Reference | MI |
Altitude | msl bound lower : 1230 msl bound upper : 1520 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : dtw tower : ptk |
Operator | general aviation : corporate |
Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | descent : approach landing other |
Route In Use | approach : straight in enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : commercial pilot : atp |
Experience | flight time last 90 days : 50 flight time total : 4200 flight time type : 1800 |
ASRS Report | 223905 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | altitude deviation : overshoot non adherence : far non adherence : published procedure other anomaly other other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Approach had told us to expect a DME localizer back course to runway 27L, so we set the instruments for that approach. At about 15 mi from the airport, detroit said the WX conditions were going down and to now intercept the localizer for runway 9R. At this point, we were rushing to set up for the new approach. The 9R approach at ptk is normally an ILS, however, the GS was OTS. I reviewed the approach plate and read what I thought were the localizer 9R mins. After the review, we were cleared for the localizer 9R approach. After passing the OM I started our time and used our LORAN as a xchk for distance to the airport. The copilot started his descent to 1230 ft MSL. Upon reaching 1230 ft we did not see the runway or lights. We still had time to go, so we continued. At approximately 1.5 mi, I elected to turn off the landing lights in an attempt to see the runway lights in the foggy conditions. Very shortly thereafter, we did see the runway. I then asked the copilot for the controls due to the lower than anticipated visibility. I made the landing without incident. Pontiac tower had called the RVR at 6000 ft, I would estimate 3000 ft because I could only see half of the 6200 ft runway. After taxiing off the runway I had a feeling something about the approach was not normal. After shutting the aircraft down I rereviewed the approach plate and discovered that I had misread the mins. I had read the ILS mins with MM OTS, not the localizer only min which is 1520. In retrospect, I can't believe I made such a stupid mistake and I am lucky to be here. I think the problem was caused by being rushed and being tired -- we had already flown 4 approachs to mins. Turbulence in a night environment. I think a good solution to this kind of problem is to have the copilot read the approach plate as well as the captain and verify what each other has read. Then make sure the mins make sense, like 250 AGL for a non precision approach? I also think it would have been a good idea to have detroit revector us and give us more time to set up properly, especially when we were tired. I have really learned a lesson from this experience!
Original NASA ASRS Text
Title: IAP LOC APCH TO BELOW MINS.
Narrative: APCH HAD TOLD US TO EXPECT A DME LOC BACK COURSE TO RWY 27L, SO WE SET THE INSTS FOR THAT APCH. AT ABOUT 15 MI FROM THE ARPT, DETROIT SAID THE WX CONDITIONS WERE GOING DOWN AND TO NOW INTERCEPT THE LOC FOR RWY 9R. AT THIS POINT, WE WERE RUSHING TO SET UP FOR THE NEW APCH. THE 9R APCH AT PTK IS NORMALLY AN ILS, HOWEVER, THE GS WAS OTS. I REVIEWED THE APCH PLATE AND READ WHAT I THOUGHT WERE THE LOC 9R MINS. AFTER THE REVIEW, WE WERE CLRED FOR THE LOC 9R APCH. AFTER PASSING THE OM I STARTED OUR TIME AND USED OUR LORAN AS A XCHK FOR DISTANCE TO THE ARPT. THE COPLT STARTED HIS DSCNT TO 1230 FT MSL. UPON REACHING 1230 FT WE DID NOT SEE THE RWY OR LIGHTS. WE STILL HAD TIME TO GO, SO WE CONTINUED. AT APPROX 1.5 MI, I ELECTED TO TURN OFF THE LNDG LIGHTS IN AN ATTEMPT TO SEE THE RWY LIGHTS IN THE FOGGY CONDITIONS. VERY SHORTLY THEREAFTER, WE DID SEE THE RWY. I THEN ASKED THE COPLT FOR THE CTLS DUE TO THE LOWER THAN ANTICIPATED VISIBILITY. I MADE THE LNDG WITHOUT INCIDENT. PONTIAC TWR HAD CALLED THE RVR AT 6000 FT, I WOULD ESTIMATE 3000 FT BECAUSE I COULD ONLY SEE HALF OF THE 6200 FT RWY. AFTER TAXIING OFF THE RWY I HAD A FEELING SOMETHING ABOUT THE APCH WAS NOT NORMAL. AFTER SHUTTING THE ACFT DOWN I REREVIEWED THE APCH PLATE AND DISCOVERED THAT I HAD MISREAD THE MINS. I HAD READ THE ILS MINS WITH MM OTS, NOT THE LOC ONLY MIN WHICH IS 1520. IN RETROSPECT, I CAN'T BELIEVE I MADE SUCH A STUPID MISTAKE AND I AM LUCKY TO BE HERE. I THINK THE PROBLEM WAS CAUSED BY BEING RUSHED AND BEING TIRED -- WE HAD ALREADY FLOWN 4 APCHS TO MINS. TURB IN A NIGHT ENVIRONMENT. I THINK A GOOD SOLUTION TO THIS KIND OF PROBLEM IS TO HAVE THE COPLT READ THE APCH PLATE AS WELL AS THE CAPT AND VERIFY WHAT EACH OTHER HAS READ. THEN MAKE SURE THE MINS MAKE SENSE, LIKE 250 AGL FOR A NON PRECISION APCH? I ALSO THINK IT WOULD HAVE BEEN A GOOD IDEA TO HAVE DETROIT REVECTOR US AND GIVE US MORE TIME TO SET UP PROPERLY, ESPECIALLY WHEN WE WERE TIRED. I HAVE REALLY LEARNED A LESSON FROM THIS EXPERIENCE!
Data retrieved from NASA's ASRS site as of July 2007 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.