37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1045002 |
Time | |
Date | 201210 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PHL.Airport |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Vectors Visual Approach |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Inflight Event / Encounter Wake Vortex Encounter |
Narrative:
Our flight was vectored for a visual approach to runway 35 in phl. We were cleared for the visual by the approach controller and switched to the tower frequency of 118.5. Upon check on with the tower [we] were asked to slow at least 20 KTS 'traffic to follow through the intersection is over the bridge'. We slowed the aircraft from 170 KTS which was given by the approach controller to our approach speed of approximately 142 KTS. The proceeding aircraft landing on 27R was an airbus A320. They landed and passed through the intersection ahead of our arrival. As we passed through 100 ft AGL we encountered the front side of the wake from the airbus followed by the backside of their wake. As we passed through the backside of the wake we touched down firmly. We exited the runway and taxied to the gate normally and deplaned normally. After further discussion about the landing; we felt that it most likely was not a hard landing but we were unsure. I contacted maintenance controller and made an entry in the aircraft logbook.this event was a matter of timing; the wind was just right; our timing behind the airbus was just right; etc. If we would have passed behind the airbus 5; 10; 15 seconds later; we would not have encountered the wake during the flare and touchdown. I understand that phl is a rare complex and situation for ATC; but I think there is an urge to make it work. I think there should be some guidance on how close we can cross through the intersection behind the preceding arrival for 27R.
Original NASA ASRS Text
Title: CRJ-200 Captain reported a wake vortex encounter on approach to PHL that resulted in a hard landing. The reporter suggests perhaps a different ATC procedure could help avoid future incidents like this one.
Narrative: Our flight was vectored for a visual approach to Runway 35 in PHL. We were cleared for the visual by the Approach Controller and switched to the Tower frequency of 118.5. Upon check on with the Tower [we] were asked to slow at least 20 KTS 'traffic to follow through the intersection is over the bridge'. We slowed the aircraft from 170 KTS which was given by the Approach Controller to our approach speed of approximately 142 KTS. The proceeding aircraft landing on 27R was an Airbus A320. They landed and passed through the intersection ahead of our arrival. As we passed through 100 FT AGL we encountered the front side of the wake from the Airbus followed by the backside of their wake. As we passed through the backside of the wake we touched down firmly. We exited the runway and taxied to the gate normally and deplaned normally. After further discussion about the landing; we felt that it most likely was not a hard landing but we were unsure. I contacted Maintenance Controller and made an entry in the aircraft logbook.This event was a matter of timing; the wind was just right; our timing behind the Airbus was just right; etc. If we would have passed behind the Airbus 5; 10; 15 seconds later; we would not have encountered the wake during the flare and touchdown. I understand that PHL is a rare complex and situation for ATC; but I think there is an urge to make it work. I think there should be some guidance on how close we can cross through the intersection behind the preceding arrival for 27R.
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.