elihoole/asrs-aviation-reports huggingface dataset:
Date: 201301
Local time of day: 1201-1800
Location: PCT.TRACON, VA
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
Airspace: Class B IAD
ATC / advisory: TRACON PCT
Aircraft component: FMS/FMC
Reporter organization: Corporate
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: When departing IAD we were instructed to fly direct to PAUKI (POO-key). I read back direct to PAUKI (POO-key). Potomac Departure then assigned a frequency change to a different Potomac Departure [Controller] and we checked in with our altitude and informed [them] we were direct to PAUKI (POO-key). The new Potomac Departure [Controller] assigned a higher altitude which we read back. A moment later Potomac Departure asked if we were direct FLUKY (FLEW-key). I responded; do you want us direct to PAUKI (POO-key) or direct to FLUKY (FLEW-key)? He said turn direct to FLUKY (FLEW-key). We immediately turned direct to FLUKY (FLEW-key). I'm not sure how this could have been avoided. We were assigned PAUKI; so we flew direct to PAUKI. The next Controller seemed to think we should be direct to FLUKY; although we were given direct to PAUKI. He then assigned us direct to FLUKY; so we turned direct to FLUKY. Maybe; if correct pronunciations were given in the notes of arrivals and departures; they would aid in situations similar to this one.




Synopsis: After departing IAD a flight was cleared direct FLUKY but the crew heard PAUKI which was activated in the FMC. ATC questioned the track deviation then recleared the flight direct FLUKY.
Date: 201601
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload; Situational Awareness; Time Pressure; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Physical Injury / Incapacitation
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Female passenger had heart attack symptoms; medical announcement made doctor/surgeon on board. Passenger placed on O2 and vitals taken. Doctor asked for Automatic Electronic Defibrillator (AED) to monitor heart rhythms as he said she was in tachycardia. Landed with passenger laying on back galley. She had vomited and defecated all over the galley floor. Paramedics met aircraft and took passenger and her family off first; Captain informed me after event he was unable to get med link. He said he had texted them in flight; but received no response. He stated that since direct access to med link via phone has been removed this has been a constant problem.




Synopsis: Flight Attendant reported a passenger illness which a passenger physician diagnosed as a heart attack. O2 was administered and Automatic Electronic Defibrillator (AED) monitored heart rhythms until paramedics removed ill passenger.
Date: 201506
Local time of day: 1801-2400
Location: ZBW.ARTCC, NH
Flight conditions: IMC
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZBW
ATC / advisory: Center ZBW
Second aircraft: B747 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: Experienced wake turbulence about 45 minutes into the flight while level at FL350 in mostly smooth flight conditions and seatbelt sign illuminated. It lasted perhaps 1 second; but most certainly got our attention. I knew the flight attendants (FAs) were preparing to serve the passengers and most importantly were not strapped in. An immediate call to check on them revealed that they were OK including the passengers. However one of the FAs had steam from the oven touch the skin on one of her arms. I inquired a few times during and after the flight; but every time she advised me she was fine. We advised ATC and were told that a B747 had crossed our path about 2 minutes earlier at the same altitude.Crossed flight path of B747. We were not advised of the crossing traffic and the vortex of the B747 had not yet descended sufficiently below our flight path. Weather conditions off and on IMC.More separation. ATC advice of crossing traffic.




Synopsis: B757-200 Captain reported encountering wake turbulence at FL350 when the crossed the flight path of a B747 operating at the same altitude.
Date: 201702
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Jet/Long Ranger/206
Operator: Personal
Flight phase: Parked
Aircraft component: Main Rotor Brake
Reporter organization: Personal
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Anomaly: Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: MEL; Procedure
Primary problem: Procedure

Narrative: I am self-Reporting to cover what has been called a need for an Out of Service event which was accomplished during In Service time (I.E. MEL Violation to Undocumented Maintenance). I was called into my base in order to defer (MEL) the Bell 206 rotor brake system. I followed the MEL instructions and inspected the system and safetied the rotor brake handle in the up position. The aircraft had been called out of service for maintenance for this MEL and after my inspection and safetying the handle and placing INOP sticker; the aircraft was returned to service with MEL active. I proceeded home for the night. I was then called by my lead mechanic and asked to return to the base to verify that the servicing of the system was in fact okay to avoid an MEL that could be erroneous. I returned to the base. I was told by the pilot that if I cut the safety on the handle I would be in violation of the MEL; so he thought. I called my lead mechanic and relayed this info to see if I should take the aircraft back out of service. It was explained to me this was not needed as we were not removing the MEL and that the safety was a simple precaution for after flight shutdown which I would be able to assure that the safety was back in place before the pilot got in the helicopter and he was to be there with me besides this fact. Servicing has been called into question without being out of service; but has not in the past been a requirement to need to take the aircraft out of service. I cut the safety on the rotor brake handle and serviced the reservoir for the system and insured there was no air in the system by slightly opening the service port on the rotor brake caliper after pumping the rotor brake handle for pressure. No air was present and the reservoir was full and the rotor brake was still in an unchanged and undisturbed state rendering the MEL still unchanged and the safety was reapplied to the rotor brake handle and verified by the evening pilot. I am submitting this [report] because I am not certain that a violation occurred under my companies MEL required procedures. I acted according to instructions from my supervision and also acted in what I believe to be a reasonable manner relating to the call to follow this order. I do not believe I intentionally did anything of a violation nature and not sure if a violation even occurred.




Synopsis: A Maintenance Technician reported that he serviced the rotor brake system on a Bell 206 after it was deferred.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After approximately 1:10 hours flight time in Aircraft X crew noticed strong fuel and oil odors in the cockpit. Odors came up every time when selecting power below approx. 15'MAP regardless of airspeed; pitch or bank. Crew discontinued the approach at [private airport]; opened the canopy to ventilate the cabin and diverted back to ZZZ. Thereafter; Crew contacted maintenance. Crew contacted flight surgeon for physical examination.




Synopsis: Flight Instructors reported strong fuel and oil odor in cockpit.
Date: 202004
Local time of day: 1201-1800
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Viking
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine Exhaust System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While I was at 5;500 ft. in cruise I heard a loud bang and the engine started to run rough. I immediately turned off the autopilot and contacted Approach and told them I had engine problems and I needed [priority handling]. They informed me that I had one [airport] to the south 3 miles; one to the north 5 miles and one to the east at 15 miles.I immediately turned to the south and proceeded to configure the plane for best glide and pulled the throttle back to idle.I set up a base leg to [the] runway with gear and flaps up. Once I was on final I dropped the gear and lowered flaps to half. I was a little high on short final and applied full flaps. I touched down right on the numbers and was able to taxi to parking.We immediately called FSS and told them we were safe on the ground and to please relay that to Approach.When the fire department arrived I informed them that everything was okay and it was just a broken muffler that caused the landing.




Synopsis: Bellanca Viking pilot reported that a rough running engine resulted in a precautionary landing.
Date: 201507
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise; got a Hydraulic System (Hyd) 1 off alert.  With loss of quantity we ran the Hyd 1 off and Hyd 1 failure checklist.  Decided to land at [destination] using their longest runway.  Landed uneventfully.  Stopped and had fire crew look over our airplane.  They told us we had fluid leaking out of port side of airplane.  We shut down the engines and got a tow back to the ramp.  Old airplane


Second narrative: Hydraulic fluid in System 1 leaked to a point where the system controller shut down the engine driven pumps in the #1 engine. Brake System 1 accumulator also had a slow leak which became evident only after the hydraulic pumps were shut off.


Synopsis: Air carrier flight crew reported that they received an alert indicating loss of Hydraulic System 1. A safe landing was made at their destination.
Date: 201910
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Windshear; 10
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: While in final landing phase at ZZZ on Runway XXL; I landed approximately 800 ft. down the runway; past the numbers; a little left of the runway center line. After touching down; a strong crosswind buffeted the aircraft from the right side. This resulted in pushing the aircraft into the grass approximately 5 ft. for about 10 ft. I then returned to the runway. When the left wheel went off the runway; it hit a standing landing light. This resulted in minor aircraft skin damage; which is being repaired. I believe there were several factors that led to this event. As I stated earlier; the strong wind gust was the major factor after touchdown. I am not sure if I also did not hit some wake turbulence as a 737 had landed prior to my arrival at XXL. Finally; I should have; after touchdown; held a more deflected aileron position. I'd take evasive action on touchdown to regain lateral control of the aircraft; and felt that if I was too heavy on the brakes; it would result in the aircraft skidding instead of rolling into the grass.




Synopsis: Small aircraft Pilot reported runway excursion due to inability to maintain directional control on landing.
Date: 201402
Local time of day: 0601-1200
Location: PDX.Airport, OR
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZSE
ATC / advisory: Center ZSE
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness; Human-Machine Interface
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Procedure
Primary problem: Procedure

Narrative: Descending into PDX via HHOOD2 RNAV arrival; JKNOX transition; [we] had 10;000 FT set in altitude preselect for crossing restriction at HHOOD. [I] failed to catch; as pilot not flying; [our] descent below 13;000 FT (MEA) prior to BAYYR Intersection. SEA Center asked to verify maintaining 13;000 and issued clearance to maintain 13;000 until BAYYR. [We should have] focused on altitude restrictions highlighted in arrival page boxes and displayed on MCDU and ND screens. In the future; [I] will expand my scrutiny to include published MEAs as well. Event spotlights limitation of iPad format to highlight published information. Also; redesign of arrival plate to include MEAs as restrictions in boxes might be helpful.


Second narrative: I was pilot flying the HHOOD2 approach to PDX landing west. We were assigned to descend via HHOOD2 landing west. I and the pilot not flying verbally discussed our next crossing altitude at HHOOD of 10;000 FT minimum. Approach called us on the radio and asked our altitude; which was 12;500. There is no 13;000 FT box at the fix prior to HHOOD for crossing. There is a small MEA 13;000 FT on the leg portion of the approach. Both pilots missed this 13;000.


Synopsis: Medium Transport flight crew descended below the MEA at an intermidiate fix due to having programmed a lower crossing restriction for the next fix on the arrival. Altitude deviation noted by ATC.
Date: 202005
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Small Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Contributing factors: Chart Or Publication; Human Factors; Procedure; Airspace Structure
Primary problem: Human Factors

Narrative: Enroute from ZZZ to ZZZ1 on an IFR clearance at FL330. Approximately 5 minutes from ZZZZZ; the Center Controller attempted to issue a revised clearance to fly the arrival. I did not accept the clearance as the aircraft I was operating can not comply with the note on the arrival clearly stating the aircraft must be capable of 280 kts or greater. The maximum speed in Aircraft X is 250 kts. Notes on published charts are legally binding for the pilot. I requested to stay on the arrival as this is a legitimate alternative to the STAR for ZZZ arrivals. The controller then threatened me with an indefinite hold until I chose to comply with his clearance to do the STAR which I can not legally accept. He finaly decided to clear me for the arrival which has a note saying GPS equipped turbojets must file the STAR.I realize that the problem here is the ridiculous and ambiguous Arrival procedures of ZZZ TRACON. That is another issue. My safety concern here is that an FAA Air Traffic Controller attempted to extort me with indefinite delay and possible fuel starvation if I did not accept and comply with a clearance I could not legally accept.




Synopsis: Pilot reported ATC tried to force him to accept an arrival that exceeded the performance of the aircraft.
Date: 202102
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
Aircraft component: Horizontal Stabilizer Trim
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Regained Aircraft Control; Flight Crew Overcame Equipment Problem; Flight Crew Landed As Precaution; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was Pilot Flying. Just after liftoff; the nose trim ran high speed nose up on its own. I waited a quick moment and told the Captain that I was not doing that trim command; and then pushed forward on the yoke to stop the runaway. After retracting the flaps; I relaxed forward pressure and the trim continued nose up runaway at slow speed. I pressed the electric time nose down on the yoke; and the up trim stopped its uncommanded nose up runaway. Then we ran the Stabilizer Runaway Checklist and returned back to ZZZ uneventfully.


Second narrative: During takeoff from ZZZ; at approximately 300 ft. AGL; the aircraft trim began running continuously; high-speed; in the 'Nose-Up' direction. The F/O (First Officer) stopped the trim by pushing forward on the yoke. This action stopped the trim movement. At 1;200 ft. AGL; after retracting the flaps; the trim began running again; continuously 'Nose-Up' in the slow-speed mode. This time the F/O used the Electrical Trim switch in the opposite direction and this action stopped the movement. We ran the Runaway Stabilizer Checklist and returned to ZZZ for an uneventful approach and landing.


Synopsis: Pilot reported a runaway stabilizer trim system and elected to air turn back and make a precautionary emergency landing.