elihoole/asrs-aviation-reports huggingface dataset:
Date: 201807
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Communication Breakdown; Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors; Airport
Primary problem: Human Factors

Narrative: While departing ZZZ we were holding short of Runway 22R at intersection W awaiting our take off clearance. Tower instructed us to line up and wait Runway 22R at intersection W which I read back. I initiated my before takeoff flows and the Captain asked for the before takeoff checklist which I verbally read and completed. The Captain then taxied the aircraft across the hold short line onto 22R. While still taxiing into position Tower gave us takeoff clearance for Runway 22R intersection W which I acknowledged with a read back. Without bringing the aircraft to a stop the Captain aligned us with the centerline and positively transferred the controls to me. After receiving control of the aircraft I stood up the thrust levers to 40% N1. While the engines were still spooling up to 40% the Captain and I simultaneously observed a 737 on a taxiway further down the right side of 22R approaching the hold short line. The Captain and I agreed that it was going to cross the hold short line onto the runway. I immediately brought the thrust levers to idle and applied the brakes bringing the aircraft to a stop. After the aircraft was stopped Tower cancelled our take off clearance which we acknowledged with a read back. Without stopping at the hold short line the 737 crossed the runway from right to left. Once it was clear of the runway Tower issued us a new take off clearance which was read back. The takeoff was then completed as normal. While I do not recall hearing the 737 receive clearance to cross the runway it may have been talking to a different controller; or it may have deviated from a clearance. It could have been a case of two aircraft receiving different clearances for the same runway at the same time. This incident highlights the importance of remaining vigilante at all times when near a runway; as well as monitoring the radio for other aircraft who may conflict with our own instructions.


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


Synopsis: Embraer 175 flight crew reported a rejected takeoff due to a runway incursion down field.
Date: 201504
Local time of day: 1201-1800
Location: GSO.Airport, NC
Flight conditions: IMC
Light: Daylight
Aircraft: Caravan 208B
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class C GSO
ATC / advisory: Tower GSO
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness; Workload
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Arriving GSO being vectored for ILS 5R everything set up for 5R. While turning base for ILS 5R preceding Aircraft (AC) had a problem and was delaying on runway. ATC advised descend from 4;000 feet to 3;000 feet expect 5 Left localizer. I started descent to 3;000 and reset approach in radios to 5L. Rushed to change and set up approach. I was given a late turn to intercept and overshot localizer. That was followed by a turn to 080 to intercept maintain 3;000 till established clear for approach switch tower 119.1. I corrected back to intercept the localizer checked in with tower and was cleared to land. Intercepting the localizer I was now good to descend to 2;500 feet and was still above 3;000 feet descending. I mistook what I later identified as the VSI bug (that was about -450 fpm) as being slightly above glide slope and continued what I thought was slightly above glide slope descent. I broke out about the same time tower said we have a low altitude alert check your altitude. I stopped descent and could see I was lower than glide slope as field was further ahead. Tower asked me to confirm altitude 1;780 and I did. I then noticed green diamond bug had appeared I now realized that I had mistaken the glide slope indicator I maintained altitude at 1;780 joined real glide slope and landed.When they gave the late change to 5 Left I should have asked for a box around until I had everything set up primary and backup. My acceptance left me rushing to catch up leading to mistakes. when identified I was beneath the cloud deck on localizer below glide path 1;780 feet; joined glide path straight ahead and continued to landing.




Synopsis: A C208 pilot reports being assigned the ILS 5R at GSO initially then switched to ILS 5L due to an aircraft on the runway. The late change to 5L results in an overshoot of the localizer and an early descent due to mistaking the Vertical Speed Indicator (VSI) bug; at -450 FPM for the glideslope indicator. Tower then issues a low altitude alert at 1;800 feet and descent is stopped until the glideslope is captured from below.
Date: 201409
Local time of day: 1801-2400
Location: LGA.Airport, NY
Light: Dusk
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B LGA
ATC / advisory: Tower LGA
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On approach to Runway 4 at La Guardia the First Officer (pilot not flying) said that we just about hit something off the right side of the aircraft and she thought it was a drone. We were at approximately 1;700 FT. After we landed and got to the gate we were discussing this because I never saw it when a passenger stepped in and asked if that had been a drone on final. We then called Clearance on the radio. They took the info and gave us a telephone number for the Tower. We then contacted the Tower and reported what the First Officer had seen.


Second narrative: On approach to Runway 4 into LGA at dusk on a VMC day; I saw an object approximately 300-500 FT below and to the east of the final approach course. We were just outside of NORAY at about 1;900 FT. It appeared to be an aircraft; but it wasn't showing on TCAS. I told the Captain. As we got closer; it was silver and I thought it was a mylar balloon. Then as it passed underneath us on the east side of our course; I thought it may be a UAV and told the Captain this. After parking; a passenger stopped by the cockpit to ask if we saw the drone over Brooklyn. The Captain reported it to LGA Clearance; who told him to tell the Tower. He reported it to the Tower. The Tower said others had reported seeing it; too. I'm not a drone expert; but this didn't look like the drones I've seen before so I'm not 100% certain that it was a drone. It was all silver and from above looked like pipes wound around each other; almost like a small intestine looks. I didn't notice any other markings on it. It did not appear to be moving higher in altitude or closer to us. A course and/or altitude deviation was not required to avoid it.


Synopsis: CRJ700 First Officer reports seeing an object; possibly a UAV or a balloon; pass below her aircraft at 1;900 FT during approach to Runway 4 at LGA.
Date: 201704
Local time of day: 0601-1200
Location: CZYZ.ARTCC, ON
Light: Daylight
Aircraft: EMB-505 / Phenom 300
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
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: Human Factors; Procedure
Primary problem: Human Factors

Narrative: ATC rerouted us and changed fixes. They cleared us to DERLO and we typed in DELRO in the FMS; no significant changes appeared. We thought we were heading in the right direction.  ATC queried us about where we heading; we told them DELRO; they then re spelled the fixed and we proceeded to DERLO. Caused by a typo in FMS and two fixes sounding the same. Typed in the correct fix and proceeded to DERLO. Should always have the phonetic spelled from ATC and type in the correct letters.




Synopsis: EMB505 Captain reported being cleared to DERLO but DELRO was entered into the FMC. ATC detected the error and reissued the clearance.
Date: 201912
Local time of day: 1201-1800
Location: RIL.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: CTAF RIL
Second aircraft: Medium Transport
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Other / Unknown; Training / Qualification
Anomaly: Conflict Ground Conflict; Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: I was taxiing Runway 26 at RIL. I allowed a corporate Jet to pass in front of me onto the taxiway.  It was so obvious that I was politely deferring to the Jet that the pilot verbally thanked me over the radio for allowing him to pass in front.  I was following the Medium Transport at what seemed an appropriate distance. I followed the taxiway center line to the designated run up area; as far from the hold short line as is possible. I was about to turn my plane to face the Jet holding short of the runway; just to be safe rather than align to the prevailing wind.  Without warning my plane was violently thrown on its right wing and flipped onto its nose by the Jet Blast of the Medium Transport. It turns out; without verbalizing his intentions; the pilot of the jet decided to get out ahead of another plane on final and used gobs of power to maneuver onto the runway.  When my plane was already on its side; I heard the pilot report 'He was taking the immediate.' and subsequently reported his take off roll.  There are audio and video recordings showing all factual events I described and procedures were followed. My plane when it was damaged was in the designated run up area around 300 feet away from the hold short line.  Obviously; the pilot forgot I was behind him and was just concentrating on an expeditious departure.  His actions; though unintended were reckless and caused significant damage to my plane. I believe he was unaware even; of the event.




Synopsis: Small aircraft pilot reported while taxiing; his aircraft was damaged due to jet blast from a departing aircraft.
Date: 201706
Local time of day: 1201-1800
Location: ZLA.ARTCC, CA
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: We were assigned the DOTSS 1 RNAV Departure. We departed 25L; somewhere between DOCKER and WEILER we were given Direct PEVEE. We were also given 280 Knots when able. The controller gave us a couple of headings; and we eventually rejoined the departure. Before he handed us off; he told us to expect HOMER at FL240. On reviewing the MCDU we realized we were not going to make the restriction. We informed him; at that point he gave us a number to call. I believe by not staying on the departure it caused us not to be able to make the restriction; also we were heavy. By staying on the SID should have rectified the problem.


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


Synopsis: A321 flight crew reported that they were unable to make the crossing restriction due to the shortened SID and having to fly vectors with speed controls.
Date: 201412
Local time of day: 1201-1800
Location: COI.Airport, FL
Flight conditions: VMC
Weather elements / visibility: CAVU; 50
Light: Daylight
Aircraft: Cheetah; Tiger; Traveler AA5 Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E F11
ATC / advisory: TRACON F11
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Rotorcraft; Flight Crew Multiengine
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: In cruise flight while scanning for traffic and birds; I noticed what appeared to be a quad copter UAV in level flight; slightly below my altitude at the 2 O'clock position going in the opposite direction. It passed off our right wing. Coordinates of the encounter were:  28.40 Degrees North; and 80.68 Degrees West; over Merritt Island Florida.  The location is close to a busy GA Airport; COI; and just south of the Kennedy Space Center restricted area; close to Port Canaveral with cruise ship operations. Clearly an illegal and potentially dangerous operation in the airspace with implications for safety as well as port security and national security.




Synopsis: A pilot reports a quadcopter UAV at 1;500 feet just south of the Kennedy Space center restricted area; near COI airport.
Date: 202109
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Military
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Flight Engineer / Second Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On landing roll out on Runway XX an opposing Cessna was trying to land Runway YY. We angled to the side of the Runway. The Cessna finally did a very low altitude go around. Very close call.




Synopsis: Pilot reported taking evasive action during landing when another aircraft attempted to land on the opposing runway.
Date: 202201
Local time of day: 0601-1200
Location: IAD.Airport, DC
Weather elements / visibility: Windshear
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower IAD
Aircraft component: Central Warning/Master Caution
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Weather
Primary problem: Ambiguous

Narrative: Clear skies; winds 340/3; temp -7. Deiced trace frost at the Gate. Good weather and no convective activity through local area. We departed Runway 30 and passing approximately 100 kts. there was a predictive wind shear warning. After a quick mental assessment of local conditions and the possibility of a high speed abort I opted to continue. We had no secondary indications; no fluctuations in airspeed or reports from the recently departed air carrier in front of us. During departure we experienced no anomalies.I've done two go-arounds over the last few weeks (one for low weather and one for an unstable approach) and experienced the same operational stresses that everyone else has recently but this was one of my toughest decisions in recent memory. I know what the manual says regarding predictive windshear guidance but the FO (First Officer) and I debriefed out of 10;000 feet and we were both in agreement that under the circumstances; with the conditions we were encountering; that continuing was the best course of action.


Second narrative: During takeoff roll above 80 kts. (I believe around 100 kts.) we had a predictive wind shear alert. Due to the current weather conditions we believed this message appeared to be an anomaly. The weather was clear skies; temp -7; calm winds (130/4) and no convective activity. Neither the previous aircraft that took off right in front of us nor Tower mentioned any wind shear conditions. Our takeoff was normal and we did not encounter any wind shear; airspeed fluctuations or turbulence.After re-reading the FOM; [Flight Handbook] and Ship Handbook regarding wind shear; I will now be more assertive stating the wind shear alert; possibly with an abort or go-around depending on the situation. It's best to always error on the side of safety.


Synopsis: Air carrier flight crew reported receiving a predictive wind shear warning passing 100 kts on the takeoff roll at IAD. They continued the takeoff because there were no secondary indications of wind shear.
Date: 201204
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 152
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Cross Country VFR Training flight. Time enroute - 3 hours 35 minutes. Engine quit. Notified TRACON; they gave vectors to [a nearby airport]; decided we were not going to make it. Thought about [another airport]; decided too far. [I] chose landing field on southeast corner of [a] park. Open paved area; no one in vicinity. [I] performed emergency landing per POH check list.According to POH performance data; [endurance] should have been approximately 5.4 hours; allowing for 4.0 hours of flight with 1/2 hour VFR reserve. Apparent fuel exhaustion; approximately 2.0 gallons of fuel removed from aircraft.




Synopsis: A C152 Instructor reported engine failure due to fuel exhaustion. A safe forced landing was executed in a nearby park.
Date: 202006
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Confusion; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Other unknown
Result: General None Reported / Taken
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: I am concerned that in previous report responses from airline; they said the policy to relay information and not enforce was not in any airline curriculum and in reviewing the mask policy I was reading the safety message and in this document [the] airline printed that your role is to relay the policy information; not enforce compliance. Why is this in a safety message if it isn't in the Airline's curriculum?




Synopsis: Flight Attendant reported confusion about airline policy relating to the face mask policy.