elihoole/asrs-aviation-reports huggingface dataset:
Date: 201605
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Initial Approach; Landing
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Communication Breakdown
Second reporter function: First Officer
Anomaly: Deviation / Discrepancy - Procedural Landing Without Clearance
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were late arriving after departing late due to lightening [at the departure airport] that had closed the ramp and the same storms forced a routing increasing the flight time. Schedule was not an issue and we were not pushing the field to make up time. Once arrived in the area; it was VMC with 10SM visibility (actually closer to 20SM). We were cleared a visual approach approximately 16 miles from runway 33L at 6;000 feet MSL after being instructed to descend to 4;000. Pilot Flying (PF) was just a bit slow to descend out of 6;000 feet and Pilot Monitoring (PM) prompted PF to start down.The aircraft continued to be high on profile and PF called for flaps 1 and selected LVL CHG 203 knots. PM had the VOR frequency to note the 10 DME/3;000 feet restriction and was instructed to contact Tower approximately 8 NM out. While the gear was down; the PF failed to select a lower speed in the window; which caused the auto throttles to increase power; although the aircraft was already high on profile. The PM failed to notice the 203 in the speed window. PM became task saturated; resulting in PM's failure to switch to Tower while directing PF to disconnect the auto throttles; pull the nose up to get below 195 knots; in order to select flaps 15 and continue on profile.Crew was able to track flaps on speed and accomplished the Before Landing Checklist. The runway was clear and everything looked like a normal approach from 1;000 feet AGL. Once turning off of the runway; the Crew noticed they were still on Approach frequency as they switched to Ground. Ground didn't mention anything except taxi instructions to the gate.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B737NG flight crew reported becoming distracted; high on profile; and landing without clearance from the tower.
Date: 201207
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Nose Gear Wheel
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: I was changing the left nose tire [on a B767-300] because it showed signs of wear. I used the correct Maintenance Manual 32-45-02; Page 401. I used the new tooling designed to release when a spacer is missing. I believe I installed all parts and retorqued tire correctly. The company informed me that they found the washer not installed on tire next to retaining nut. The plane never incurred any damage or delay to my knowledge.




Synopsis: A Line Mechanic was informed that a washer next to the axle retaining nut for the left nose tire was found not installed on a B767-300 aircraft; after he signed for the tire change.
Date: 201208
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
Aircraft component: DC Generator
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness; Troubleshooting; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Became Reoriented
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: I was flying VFR above a scattered layer and noticed my radio lights growing dim and the ADF not working properly. I looked at the ammeter for the generator and it was on zero. I made a 180 degree turn to return to the airport and started a cruise descent and noticed the airspeed indicator was near red line. I slowed the aircraft down and noticed that the controls were becoming mushy while the airspeed was still in the yellow arc. I then ignored the ASI and flew the plane back to the airfield by feel and without radios or a transponder. I landed without incident and the ASI read 110 KTS right when the stall warning went off just before touchdown and when I came to a full stop the ASI read 70 KTS.




Synopsis: While flying VFR; a PA28 pilot notices that the generator has apparently failed and a turn is made to return to the departure airport. During descent airspeed is noted to be near the red line but slowing produces a mushy feeling in the flight controls. The airspeed indicator is ignored and the aircraft is successfully flown to a safe landing by feel alone.
Date: 202107
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Take Off
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We commenced our takeoff normally. At around 95 kts; we got an ECAM for Y RSVR Lo Lvl and Y RSVR Lo Air Pr. The Captain initiated the abort with a max speed of approximately 100 kts. All callouts and notifications were made and we were able to taxi clear of the runway and stop. ATC notified us that we had trailed smoke so we asked him to roll the ARFF (Aircraft Rescue and Firefighting) equipment. We ran the rejected takeoff checklist and then ran the ECAMs of which there were several all relating to the hydraulic issue. ARFF indicated that we had dumped a lot of hydraulic fluid. We were towed to the gate for repairs and offloaded the passengers and bags.


Second narrative: Received a Master Caution light and ECAM during takeoff roll on Runway XXR at ZZZ and accomplished a rejected takeoff. The Master Caution and ECAM occurred at approximately 95 kts and Reject initiated between 95-105 kts. During the reject; several ECAMS displayed indicating loss of the Yellow Hydraulic system reservoir and Yellow system air pressure. At slow speed and with normal brakes and nosewheel steering available; I opted to take high speed Taxiway XX to safely clear the runway and bring aircraft to a full stop while the First Officer coordinated with Tower controller to roll the AARF (Aircraft Rescue and Firefighting) equipment as Tower stated they saw what appeared to be smoke trailing from the number two engine. While awaiting AARF response; we ran the Rejected Takeoff QRC and handled the ECAMS; started the APU and communicated with the passengers [and] inflight crew. After AARF arrival and initial inspection; we shutdown the number 2 engine with AARF on scene; then chocked the gear and shutdown the number 1 engine which had been used to keep normal brakes available. We coordinated with Operations and Ground Control for uneventful tow back to the gate for repair.


Synopsis: A320 Flight Crew reported a Rejected Take Off when the Yellow Hydraulic system showed low quantity and had to be towed back to the gate.
Date: 201606
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Test Flight / Demonstration
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Brake System
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was taxi testing the aircraft. I taxied to [the] runway; then turned around and taxied back to the ramp. I lost brakes and taxied into another aircraft. The damage to the other aircraft was minimal; and I broke my taxi light on my left wing.




Synopsis: C172 pilot reported taxiing into another aircraft following brake failure.
Date: 201901
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: EMB ERJ 190/195 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cockpit Door
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Security
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During inflight bathroom break; the cockpit door was opened. Upon FA (Flight Attendant) entering flight deck; FO (First Officer) tried closing the cockpit door. Upon closing door; the door appeared to bind. Repeated attempts were made to try and close the door however the door was extremely warped. Flight Attendant later described what looked like spring near bottom of door. Flight landed at destination with Flight Attendant guarding door with cart blocking access until landing gear extension. First Officer utilized crash axe for defense and necktie to hold door closed. Armed LEO was informed of situation and to provide assistance in unlikely event of a level 4. A non-revning FA was also able to provide assistance. Dispatch was notified along with Maintenance Control. No guidance exists for cockpit door issues in flight.




Synopsis: ERJ-190 Captain reported cockpit door jammed during cruise rendering it unlocked for remainder of flight.
Date: 201309
Local time of day: 0601-1200
Location: DEN.Airport, CO
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We departed off the North Ramp east taxi to 4E. Construction is causing delays at that intersection. We were headed to Runway 8; when we were offered 17L. We taxied ahead on EC to 17L. We have been using P7 intersection most of last month and this month. First Officer quickly started Number 2 and was working on performance data. We had been used to using P7 and accepted the data without a complete check of limits. We took the runway with a Flex setting and seemed to use more runway than usual; rotated about 1;000 FT later than normal. Out of 10;000 I had the First Officer check the data and we took off overweight from the intersection. I feel I hurried him and that caused this.


Second narrative: [Narrative 2 provided no additional information].


Synopsis: A319 flight crew reported taking off overweight because the First Officer was rushed in his calculations.
Date: 201509
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Human factors: Distraction; Situational Awareness
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: The new after start and before takeoff checklists are faulty. The new procedure requires flap configuration via flow; with no reference to take off data. It then requires an insanely detailed before takeoff checklist to be conducted during taxi out; with the result being the First Officer being heads down for an extended period and the taxiing Captain unable to properly and safely taxi and monitor what the First Officer is doing. The flap position is only checked during this long before takeoff checklist while the Captain is taxiing.The new checklist is a human factors disaster. The taxi should be treated as a sterile environment; with both pilots paying attention to the aircraft movement. Any required call outs; such as a before takeoff checklist; should be brief and to the point. It is this reason that many pilots are treating the new checklist as a threat to safety and only doing that before takeoff portion 'above the line' while parked with the brakes set.




Synopsis: B757 Captain stated he is unhappy with the new before takeoff checklist; asserting it is a 'human factors disaster.'
Date: 201705
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Human Factors

Narrative: While taxiing out on C line; a tow on B line cut over close to my line; forcing me to stop. Had I not stopped; there would have been a collision on ground with aircraft damage between the two aircraft.




Synopsis: A320 Captain reported stopping the taxi because an aircraft under tow began to drifted towards the taxiway.
Date: 201811
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Turbulence
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cooling Fan; any cooling fan
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were cruising at FL280 when I heard a buzzing noise coming from the floor on the Captain's side that lasted a couple of seconds. Then my First Officer and I smelled smoked in the flight deck. I told the First Officer to put on [the] oxygen mask and smoke goggles. We accomplished the QRH checklist and [diverted to an alternate airport].After landing; maintenance told us the #2 avionics fan shorted out and that was what probably caused the smell of smoke and buzzing noise.




Synopsis: EMB-145 Captain reported a buzzing noise and smoke in the cockpit that was later traced to a short in the #2 avionics fan.
Date: 201605
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E N90
ATC / advisory: TRACON N90
Second aircraft: Sail Plane
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: First Officer
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We had just leveled at 7000 feet over SWEET intersection on the arrival into EWR when the First Officer spotted a glider and called the traffic. We then saw the glider pass approximately 200-300 feet below the nose of our aircraft. It appeared that the glider was maneuvering to avoid us. We were headed northeast and the glider was headed west. We did not have a chance to maneuver our aircraft to avoid the glider. We did not receive a TCAS Alert because the glider did not have a transponder. ATC did not report the traffic but did say gliders had been a problem in that area when we reported the near miss. The rest of the flight was uneventful. We reported the near miss to ATC and Dispatch.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B737 flight crew reported an NMAC with a glider that was not equipped with a transponder while on approach to EWR.
Date: 202104
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Corporate
Operating under: Part 135
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Air Conditioning and Pressurizaton Probes & Sensors
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing out; EMERG PRESS ON came on; ran checklist; unable to fix; [advised ATC]; landed.


Second narrative: Climbing out of ZZZ; EMERG PRESS ON light came on; ran checklist; wouldnt turn off; [advised] ATC; landed back at ZZZ.


Synopsis: Citation flight crew reported experiencing pressurization malfunction after takeoff.
Date: 201711
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew FLC Overrode Automation; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: We were on downwind on vectors. We were expecting vectors to base. ATC issued heading of left turn 010 degrees. I slewed the bug over to the heading. First thought it was quite a big turn. Low ceilings made me think it might be a delay vector. The turn ended up being more than 180 degrees which results in the plane turn opposite the direction I moved the heading bug. Upon noticing the plane turn direction opposite what was commanded; I switched off the autopilot and corrected to a left turn. The controller corrected the heading to 110 degrees. Flight was maintained in level flight.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B787 flight crew reported that ATC issued an incorrect heading resulting in the aircraft turning the wrong direction.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 91
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was operating a ferry flight and just after departure around 400 FT; the #1 Engine torque immediately shot up to 116% with a noticeable change in yaw (and sound). My First Officer called out 'engine failure;' and while correcting for the yaw; I asked him to identify that the #1 Engine had failed and feathered. He said the engine had failed but did not feather; and I elected to immediately shut down the #1 Engine and feather it. We notified ATC of our engine failure and emergency condition. We ran the Engine Failure Checklist and circled back to land for a visual. With the Emergency Checklist not fully completed and clouds beginning to hide the airport; I requested additional vectors for the ILS in order to assure proper landing and to complete the Emergency Checklist in full. We then landed single-engine without incident.




Synopsis: DHC8-200 Captain experiences an over torque just after takeoff and elects to shut the engine down and return to the departure airport.