elihoole/asrs-aviation-reports huggingface dataset:
Date: 201205
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Other Takeoff roll
Result: Flight Crew Returned To Gate; Flight Crew Rejected Takeoff
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Just before the 80 KT call we felt a loss of thrust on the right side accompanied by a loud bang and airframe vibrations. We accomplished the RTO memory items; cleared the runway and taxied back to the gate uneventfully. After rejecting the takeoff; Tower informed us that flames were observed coming out of our right engine but they were no longer present. Fire Crews were at the gate.


Second narrative: [No substantive additional information was provided in the secondary narrative.]


Synopsis: A B737-700 flight crew rejected their takeoff about 80 KIAS due to loss of thrust accompanied by a loud bang from the right engine.
Date: 202105
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: Learjet 60
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Taxi
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; Captain
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Ground Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overrode Automation; Flight Crew Took Evasive Action
Contributing factors: Weather
Primary problem: Weather

Narrative: We were deviating to the southeast; around weather northwest of ZZZ; with the use of on board radar. We were not painting weather on the course we selected. Shortly after asking to deviate the aircraft began to climb. I turned off the autopilot and maintained wings level. Immediately thereafter we encountered numerous updrafts and downdrafts making it difficult for me to maintain altitude and airspeed. I did the best I could to maintain wings level and 'rode out' the turbulence which resulted in altitude deviations. The aircraft also banked left and right however the bank never exceeded 30 degrees in either direction. The entire encounter lasted approximately two minutes.In the future I will take on extra fuel and alter my flight plan and/or course to avoid areas of large precipitation / weather in their entirety.


Second narrative: We were at FL410.  We knew about the weather before we left.  There were some high top reports but not many.  We got closer to the line and asked for FL430.  We started on top but then went into IMC conditions.  We had our radar on the 100 mile range and pointed down so that the 50 mile line was painting the ground and any storms that were between 50 nm and 100 nm.  If there is a storm between the 50 nm and 100 nm and it is severe the ground behind it will not paint.  It will be black.  Also; if the storm crosses the 50 nm line and starts to disappear then you will top that storm.  We deviated to the left of course to an area that looked clear and was disappearing as we got closer.  So we should have topped it.  We got into the top of a buildup.  First Officer turned off the auto pilot and hand flew.  We got some rain and an updraft followed by a down draft and then numerous up and down drafts. we went up to 43;300 and I saw 41;800 on the down side.  The event lasted about 90 seconds.In the future; look to go-around the line or cross the line where there are lower tops.


Synopsis: Lear 60 flight crew reported a momentary loss of aircraft control while flying through cloud tops and encountering up- and downdrafts.
Date: 201701
Local time of day: 1801-2400
Location: LGD.Airport, OR
Weather elements / visibility: Snow; 10
Light: Night
Aircraft: Small Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: CTAF LGD
Reporter organization: Corporate
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors; Weather
Primary problem: Human Factors

Narrative: LGD airport; landed runway 12. During taxi from runway to the hangar I was following the taxiway centerline as that kept the aircraft clear of obstacles. During this taxi as I approached what is to be a left-hand turn into my parking spot the aircraft had a slight nudge and as I'm looking out the left hand windscreen my crew member said I think the right hand wing skipped over a snow berm. Post shut down and inspection the snow berm that the fiberglass radome glanced off of was not fully plowed away from the taxiway to make reflectors and edge markings clear. So as my attention was focused on the left hand turn and parking the right-hand wing was neglected.Result: division of attention was not consistent during taxi and parking.Environmental conditions: Night; low light from nearby hangars; unclear taxiway edge markings.




Synopsis: A small transport pilot reported their aircraft came into contact with a snow berm while taxiing at LGD.
Date: 201510
Local time of day: 0601-1200
Location: SNA.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class C SNA
ATC / advisory: Tower SNA
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown; Training / Qualification
Anomaly: Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: After takeoff on Runway 19L I did not correct enough for the crosswind component; and my aircraft drifted towards the departure path of Runway 19R. I was prepared to make my crosswind departure turn at 700 feet AGL. Just prior to that altitude; I commenced my turn and from the back window; noticed a B737 rapidly approaching from behind. John Wayne Tower instructed me to turn to the left as I simultaneously started a steep turn to provide traffic clearance.Contributing factors: This was my first time flying into this airport and was unfamiliar with the departure procedures. I had been given a heading by Ground Control; but no direction as to when to make this turn.




Synopsis: C182 pilot reported an NMAC with a B737 shortly after departing SNA.
Date: 201511
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: B767-300 and 300 ER
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: Central Warning/Master Caution
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While Cruising at FL 370 we received the following lights: Windshear; Speed Brakes; GRD PROX (GS INHB);only the right bulb of Pull Up; Cabin Alt; Master Caution (EICAS; ATC Fault). At the same time the Captains altimeter spun continuously; First Officer (FO) airspeed went to zero. The autopilot did not disconnect. There were no tones or audible warnings.  The QRH was referenced. About a minute later everything returned to normal with the exception of the FO altimeter. It remained failed for the remainder of the flight.  It was determined that we needed to descend from RVSM airspace after conferring with dispatch and maintenance.  It was determined by maintenance that the best course of action was a divert into ZZZ. After a discussion with the Captain of the risk factors of going into a Special Use Airport; we both agreed that it was safe to do so. The flight concluded without further incident.  I will add that neither the Captain or I are certain that weather and NOTAMS were sent to the ACARS.




Synopsis: The B767 pilot received several apparently spurious warnings which also affected some of the flight instruments. Everything returned to normal after about a minute except for the failure of the First Officer's altimeter. The aircraft was diverted to a maintenance base.
Date: 201504
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: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Normal Brake System
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Workload; Troubleshooting; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On the taxi out to take off both student and I performed initial brake check at slow speed and brake operation was normal. Continued taxi for takeoff and made two right turns with normal steering and brake operation. After crossing a runway the taxiway made a turn to the left; the student was at the controls and I noticed us veer from taxiway centerline to the right; slowly. Then after looking and verifying that she was making the correct control input on the rudder pedal and seeing the taxi continue to the left I applied my rudder and brake control to get back to the taxiway centerline and follow the left turn. With full rudder pedal deflection and full brake application on the left brake the airplane was still not controllable and exited the taxiway onto the grass at a slow speed. Upon rolling off the asphalt I shut down the engine and contacted ground and had the aircraft towed to maintenance. No damage was noted on the aircraft or on any airport equipment.




Synopsis: A C-172 Instructor reported the aircraft began veering right while taxiing while the student was under control of the airplane. The instructor took the controls and tried to turn to the taxiway but was unable and shutdown the engine as the aircraft exited the taxiway.
Date: 201812
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: Training
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure
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
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Lost Oil Pressure. Gauge indicated 0. Engine started to run really rough and so I [notified ATC] and returned to the airport for a full stop landing. Used best glide speed to ensure obstacle clearance and ended up having to do one turn over the airport to lose altitude before doing a short approach to a full stop.




Synopsis: C172 instructor reported returning to the departure airport following a loss of engine oil pressure and engine performance.
Date: 201303
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Confusion
Second reporter function: Supervisor / CIC
Anomaly: Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While working N-AR; I observed a C172 on an S-AR tag approximately 1 mile east of the airport. At the time; I thought that the C172 had executed a go-around on Runway YYR. The aircraft had arrived [at the airport] from the south. As I scanned my display; I then noticed that the C172 appeared to be turning towards the airport from the east lining up for Runway XXR. The aircraft at this point was less than a mile from the airport and I said out loud 'What's [the C172] doing'. As I spoke; I observed a limited data block in close proximity to [a C172] opposite direction departing. The tags merged. Local 1 called and pointed out [the C172] to my sector advising he was going to put him on the left downwind. R453 checked on the frequency and advised he had a near miss with [the C172]. I took the information from R453 and gave him the facility phone number so that he could discuss the event with the Front Line Manager. I advised Local 1 to instruct [the C172] to fly heading 290 and I would vector him back to final. [The C172] landed Runway YYL without further incident.


Second narrative: [A C172] inbound to [the airport] was instructed to enter the right mid-field down wind Runway YYR (via the [STAR] arrival). [The C172] entered the mid-field down wind and turned east (wrong direction) and entered a base for Runway XXR. [A C172] conflicted with [another C172]; a departure off Runway YYL. [The first C172] saw [the second C172] and turned to avoid. I observed the conflict and issued [the first C172] a 180 headings. [The first C172] did not take the heading; but turned north east. I then issued a 270 heading but [the first C172] turned east bound. I once again issued a 270 heading but [the first C172] continued east. I once again told [the first C172] to fly westbound and he finally complied. [The second C172] declared on the frequency that he had experienced a NMAC. [The first C172] was a solo student. Better pilot training by the local flight school. This student should not have been alone.


Synopsis: TRACON Controller described a NMAC between a traffic pattern arrival and a departing aircraft; the reports indicating the arrival aircraft was a student pilot who entered the pattern incorrectly.
Date: 201701
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On approach both I and the FO failed to recognize that we hadn't put the gear down at the normal time. We noticed just before/as the gear warning sounded. We should have gone around; but instinctively; the FO (who was flying) said gear down; flaps 30. I instinctively did it rather than calling for a go around. We got the gear and flaps down; and were stabilized in plenty of time; but perhaps not by the 1000 feet AGL that we should have been. I'm not sure when we got fully configured; but it was close to 1000 feet.In retrospect; we should have gone around at the first indication of being that low with the gear not down; but we both just kicked into the fix-it mode and tried to get configured how we should have already been. I don't believe we were unsafe as we landed without incident; but the safer thing would have been to go-around.The lessons are manifold. We were at the end of a long day; and felt fat dumb and happy; when we had failed to do a basic thing. Don't let yourself get into that position in the first place. However; finding yourself there; do the right thing. Don't force a bad situation. Go around; sort it out; kick yourself for being dumb; and get it right the next time.




Synopsis: CRJ-900 Captain reported they were late to lower the landCRJ-900 Captain reported being late to lower the landing gear; but elected to land rather than go-around for an unstabilized approach.
Date: 202110
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other after flight
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Fatigue; Communication Breakdown; Physiological - Other
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; No Specific Anomaly Occurred Unwanted Situation
Detector: Person Flight Crew
When detected: Other after flight
Result: Flight Crew Landed in Emergency Condition; General Work Refused
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: After landing in ZZZZ I talked to duty manager.  He asked if I was OK and then proceeded to notify me of our crew's new pairing information.  He never asked if I felt; or my crew; if we could continue on to our next flight or if we were having any physical or other symptoms following our emergency.  After notifying him that we did not want to fly again that day he told me that it wasn't that simple and that I was putting him in a difficult situation.  I said that I understood but that we had just been in a difficult situation.   He also said that I can't just make that statement.  He also wanted to know why Name;  had changed her mind after she told him on the phone that she was fine.  I explained that I was willing to pass the phone to each flight attendant so that they could each inform him of their request.  He then asked if we were unable to perform our safety and customer service responsibilities.  I said yes; we felt we were unable to do so and that it was a consensus with each flight attendant.  About an hour after landing; I felt a sudden arc like headache and felt cold in both my hands and feet.  I also experienced chills throughout my body.  I had a surge of adrenaline during the emergency incident and afterwards felt both fatigue and extreme thirst.




Synopsis: Flight attendant reported a headache; feeling cold in the hands and feet; chills throughout the body; fatigue and thirst after landing.
Date: 201707
Flight conditions: IMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E C90
ATC / advisory: TRACON C90
Aircraft component: Navigation Database
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: We were being vectored around weather/traffic for the WATSN 3 arrival to ORD. ATC gave us a clearance to proceed direct to the WATSN fix and hold as published. There is no published hold in the iPad Jeppesen app or in the FMC. We looked for the hold on the arrival chart; high and low IFR charts. No published hold exists at WATSN in our electronic Jepp charts or in our FMC database. There is a published hold on the FAA arrival chart; but not on the current Jepp arrival chart.




Synopsis: B757 Captain arriving ORD was instructed to proceed direct to an intersection and hold as publish. There was no published hold in the iPad Jeppesen app or in the FMC; but the FAA chart does depict a holding pattern at the intersection.