B757 flight crew reported on initial climb the aircraft experienced an uncommanded yaw 30 degrees to the right and they heard a loud pop then they smelled a burning odor. No evidence of fire or smoke and all engine indications were normal.
Synopsis
B757 flight crew reported on initial climb the aircraft experienced an uncommanded yaw 30 degrees to the right and they heard a loud pop then they smelled a burning odor. No evidence of fire or smoke and all engine indications were normal.
Narrative
On our initial climbout; we experienced an uncommanded yaw to the right (almost 30 degrees). It felt like we had an engine fail; though all engine indications were normal. Along with the yaw movement; there was a loud 'pop' that sounded like an explosion. Initially we suspected something hit the aircraft to cause sound and yaw motion. We both checked the EICAS and pressurization panel. All indications were normal. We started to pick up an unusual smell. It smelled like something was hot or overheating. No indication of fire or smoke in the flight deck; we did not don the oxygen mask. The smell lingered for the duration of the flight. I was starting to get a headache from the smell. As we continued; I also started to get a headache. We decided to return to the field. We [requested priority handling] as we were unsure of cause of our issues. We also wanted to have the aircraft inspected. We came back for the ILS XX; we landed without issue. Once we cleared the runway; we exited onto taxiway 1 off Taxiway 2 facing northbound. The ZZZ Crash Fire Rescue [CFR] inspected the exterior of the aircraft for damage and hot spots. None were found. We made our way to gate XX under our own power with CFR following behind us. Maintenance met the aircraft. They also noted no evidence of something hitting the aircraft. After we landed; the headaches continued. Once we were able to open the window; the fresh air helped but did not relieve it completely. We also had a little bit of nausea accompanying the headaches.
Second reporter narrative
[Report narrative provided no additional information].
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.