 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Emb-145 first officer reported a lightning strike during arrival to gsp and faulted dispatch for not warning them about the weather.
| Attributes | |
| ACN | 1437551 |
| Time | |
| Date | 201704 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | GSP.Airport |
| State Reference | SC |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 200 Flight Crew Total 1600 Flight Crew Type 60 |
| Events | |
| Anomaly | Inflight Event / Encounter Weather / Turbulence |
Narrative:
We were doing a flight to gsp and ran into some rough weather near gsp where we were struck by lightning. We tried to go to our alternate; but they were no longer taking anyone there so we went to [a new alternate] because it was the closest airport without storms around it.we decided to divert to ZZZ after we tried our planned alternate and it was closed. We had no information from dispatch with where to go next so we decided to go to ZZZ.I believe this event occurred because of a weak communication with dispatch; allowing us to go into weather that could have easily been avoided by a reroute from dispatch. Our radar in the aircraft is not near as accurate as what dispatch is showing on the ground; so therefore they should have been warning us what we were headed into; but they said nothing! We sent them a message asking where they wanted us to go since our filed alternate was closed and they were in the middle of a shift change so the response was too late; we were left to make the decision on our own! We took action on the event by deciding to go to ZZZ and get the aircraft on the ground out of the weather! In the future I will be sure to initialize better communication with dispatch throughout the entire flight about the forecast conditions at my ETA at destination airport!
Original NASA ASRS Text
Title: EMB-145 First Officer reported a lightning strike during arrival to GSP and faulted Dispatch for not warning them about the weather.
Narrative: We were doing a flight to GSP and ran into some rough weather near GSP where we were struck by lightning. We tried to go to our alternate; but they were no longer taking anyone there so we went to [a new alternate] because it was the closest airport without storms around it.We decided to divert to ZZZ after we tried our planned alternate and it was closed. We had no information from dispatch with where to go next so we decided to go to ZZZ.I believe this event occurred because of a weak communication with dispatch; allowing us to go into weather that could have easily been avoided by a reroute from dispatch. Our radar in the aircraft is not near as accurate as what dispatch is showing on the ground; so therefore they should have been warning us what we were headed into; but they said nothing! We sent them a message asking where they wanted us to go since our filed alternate was closed and they were in the middle of a shift change so the response was too late; we were left to make the decision on our own! We took action on the event by deciding to go to ZZZ and get the aircraft on the ground out of the weather! In the future I will be sure to initialize better communication with dispatch throughout the entire flight about the forecast conditions at my ETA at destination airport!
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.