37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1518896 |
Time | |
Date | 201802 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LCK.Airport |
State Reference | OH |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | Altimeter |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 110 Flight Crew Total 960 Flight Crew Type 760 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural FAR Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was acting as cfii with instrument asel student on training flight; executing the localizer 23L approach at lck; glideslope out. Previous approach reported altimeter setting was 30.21. We received [ATIS] information at lck and confirmed this with columbus approach. The student did not reset the altimeter to the lck setting of 30.16 and the instructor failed to cross-check the student's procedures. We descended to the MDA at an indicated altitude of 1;220 ft MSL after passing the FAF; at which point lck tower gave an altitude alert and confirmed the altimeter setting of 30.16. This pointed out the error of failure to reset the altimeter to local setting and we immediately executed the missed approach procedure. At the time of executing the map (missed approach procedure); we had ground visual contact but did not have the runway in sight. This situation can be avoided in a crew environment by more careful crosscheck of procedures and in any environment by closer attention to weather reports when preparing for an approach.
Original NASA ASRS Text
Title: C172 Flight Instructor reported a low altitude alert from the Tower during a localizer approach due to an incorrect altimeter setting.
Narrative: I was acting as CFII with Instrument ASEL student on training flight; executing the LOC 23L approach at LCK; Glideslope Out. Previous approach reported altimeter setting was 30.21. We received [ATIS] information at LCK and confirmed this with Columbus approach. The student did not reset the altimeter to the LCK setting of 30.16 and the instructor failed to cross-check the student's procedures. We descended to the MDA at an indicated altitude of 1;220 ft MSL after passing the FAF; at which point LCK Tower gave an altitude alert and confirmed the altimeter setting of 30.16. This pointed out the error of failure to reset the altimeter to local setting and we immediately executed the missed approach procedure. At the time of executing the MAP (Missed Approach Procedure); we had ground visual contact but did not have the runway in sight. This situation can be avoided in a crew environment by more careful crosscheck of procedures and in any environment by closer attention to weather reports when preparing for an approach.
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.