37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1123288 |
Time | |
Date | 201310 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | CLE.Airport |
State Reference | OH |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | EMB ERJ 135 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Landing |
Route In Use | STAR CHARDON |
Flight Plan | IFR |
Component | |
Aircraft Component | Flap Control (Trailing & Leading Edge) |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
We were flying the cxr (chardon) arrival. ATIS was broadcasting landings on 24L. We briefed and planned an approach to [runway] 24L. After leaving lebrn we were vectored for the approach. When we were very close to the airport approach then cleared us for the approach to 24R. We were also given the instruction to maintain 3;000 ft until 6.0 DME. I had the first officer switch the ILS frequency so we could use the glideslope and localizer as a reference for the approach. The 3;000 ft restriction leaves the aircraft above the glide path and prevents the aircraft from capturing the glideslope while on autopilot. Knowing this I elected to select autopilot off and hand fly the aircraft. As we crossed 6 DME at 3;000 ft; I made the call; 'gear down; flaps 22; landing checklist.'at about the same time approach told us to switch to tower. The first officer selected gear down; notified the flight attendant; and switched the radio to tower. However the first officer never selected flaps 22. I started a descent to capture the glideslope from above and had the aircraft stabilized on speed coming down the glideslope. Both the 1;000 ft and 500 ft calls were made. However; in all the activity the before landing checklist was somehow missed. Coming down the glideslope we received a flap warning alert.realizing the problem the first officer selected flaps 22. We elected to land the aircraft. We were on speed; on the glideslope; and descending at a normal rate; with the landing checklist completed. We touched down with flaps 22 on speed with a normal descent rate and in the touchdown zone. I feared a go-around may cause further complications if flaps 9 were selected while in transition to flap 22 a flap failure may occur further complicating the problem. I thought the safest course of action was to continue the approach and land.do not give aircraft approach changes and a crossing restriction without much time to prepare for the approach. Also the crossing restriction of 3;000 ft at 6 DME is unnecessary. It leaves the aircraft high for the approach and makes very little difference in noise abatement. We were both task saturated. I called for the items and expected them to be accomplished.
Original NASA ASRS Text
Title: When Approach changed their approach and landing clearance from 24L to 24R at CLE and to maintain 3;000 until 6 DME the flight crew of an ERJ got task saturated and the First Officer failed to set landing flaps when requested by the Captain/Pilot Flying. The error was noted by the configuration warning and a safe landing with appropriate flap extension was completed.
Narrative: We were flying the CXR (CHARDON) arrival. ATIS was broadcasting landings on 24L. We briefed and planned an approach to [Runway] 24L. After leaving LEBRN we were vectored for the approach. When we were very close to the airport Approach then cleared us for the approach to 24R. We were also given the instruction to maintain 3;000 FT until 6.0 DME. I had the First Officer switch the ILS frequency so we could use the glideslope and localizer as a reference for the approach. The 3;000 FT restriction leaves the aircraft above the glide path and prevents the aircraft from capturing the glideslope while on autopilot. Knowing this I elected to select autopilot off and hand fly the aircraft. As we crossed 6 DME at 3;000 FT; I made the call; 'gear down; flaps 22; Landing Checklist.'At about the same time Approach told us to switch to Tower. The First Officer selected gear down; notified the Flight Attendant; and switched the radio to Tower. However the First Officer never selected flaps 22. I started a descent to capture the glideslope from above and had the aircraft stabilized on speed coming down the glideslope. Both the 1;000 FT and 500 FT calls were made. However; in all the activity the Before Landing Checklist was somehow missed. Coming down the glideslope we received a flap warning alert.Realizing the problem the First Officer selected flaps 22. We elected to land the aircraft. We were on speed; on the glideslope; and descending at a normal rate; with the Landing Checklist completed. We touched down with flaps 22 on speed with a normal descent rate and in the touchdown zone. I feared a go-around may cause further complications if flaps 9 were selected while in transition to flap 22 a flap failure may occur further complicating the problem. I thought the safest course of action was to continue the approach and land.Do not give aircraft approach changes and a crossing restriction without much time to prepare for the approach. Also the crossing restriction of 3;000 FT at 6 DME is unnecessary. It leaves the aircraft high for the approach and makes very little difference in noise abatement. We were both task saturated. I called for the items and expected them to be accomplished.
Data retrieved from NASA's ASRS site as of July 2013 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.