37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1089903 |
Time | |
Date | 201305 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Component | |
Aircraft Component | Normal Brake System |
Person 1 | |
Function | First Officer Pilot Not Flying |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
We were cleared for a visual approach and I was the pilot monitoring while the captain was flying. Around the final approach fix; the captain called for gear down; which resulted in the EICAS messages brk lh fault and brk rh fault. I called out the message; and executed a go around and was given a heading and an altitude by ATC. Before the tower controller handed us off to departure; he asked us for the nature of the go around; and we told him a fault message had been received on approach and we needed to run a checklist. We were given a few step climbs in the go around up to 6;000 feet. We were given a delay vector to run the QRH. We ran the brk lh (rh) fault QRH. The QRH lead us to setting up the next approach flaps full; as well as compute a landing distance. After running the QRH we contacted dispatch as well as maintenance. We agreed that the proper QRH was run and that we would declare an emergency and land. We completed all checklists and briefed approach; and what our back up plan was. We declared an emergency and we were given a clearance to land on the long runway and had crash/fire/rescue standing by. We landed; and had all normal indications from the cockpit. We brought the aircraft to a stop on the runway and assessed the situation; talked with crash/fire/rescue and determined the aircraft was capable of taxing to the gate under its own power.
Original NASA ASRS Text
Title: EMB170 First Officer reports EICAS messages for BRK LH Fault and BRK RH Fault when the gear is extended during approach. A go around is initiated; the QRH is consulted and a normal landing ensues after declaring an emergency.
Narrative: We were cleared for a visual approach and I was the pilot monitoring while the Captain was flying. Around the final approach fix; the Captain called for gear down; which resulted in the EICAS messages BRK LH Fault and BRK RH Fault. I called out the message; and executed a go around and was given a heading and an altitude by ATC. Before the Tower Controller handed us off to Departure; he asked us for the nature of the go around; and we told him a fault message had been received on approach and we needed to run a checklist. We were given a few step climbs in the go around up to 6;000 feet. We were given a delay vector to run the QRH. We ran the BRK LH (RH) FAULT QRH. The QRH lead us to setting up the next approach flaps full; as well as compute a landing distance. After running the QRH we contacted Dispatch as well as Maintenance. We agreed that the proper QRH was run and that we would declare an emergency and land. We completed all checklists and briefed approach; and what our back up plan was. We declared an emergency and we were given a clearance to land on the long runway and had crash/fire/rescue standing by. We landed; and had all normal indications from the cockpit. We brought the aircraft to a stop on the runway and assessed the situation; talked with crash/fire/rescue and determined the aircraft was capable of taxing to the gate under its own power.
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.