elihoole/asrs-aviation-reports huggingface dataset:
Date: 201411
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Climb
Airspace: Class E ZZZ; Class G ZZZ
ATC / advisory: CTAF ZZZ; TRACON ZZZ
Aircraft component: Powerplant Fuel Distribution
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
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; Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climbout on a VFR flight passing approximately 7;500 feet MSL; the engine of a BE35 V35 Bonanza began running rough and fuel spray was seen on the windscreen.  Fuel fumes were also smelled in the cockpit.  VFR flight-following had been previously requested and provided by Approach Control.  Upon notification of engine difficulty; Approach provided a vector to the nearest airport; and queried if assistance was needed.  The pilot replied that assistance was not needed.  Approach then directed the pilot to squawk 1200 and switch to advisory frequency; to which the pilot replied with a request for the advisory frequency.  Approach provided the frequency.  During this exchange; the engine was exhibiting signs of fuel starvation and/or interrupted fuel flow; as well as continued fuel odor in the cockpit and fuel visible on the windscreen.  Upon switching to the advisory frequency; the pilot heard another aircraft in the pattern.  At this time; due to continued intermittent engine response; the pilot declared that he was an emergency aircraft and would be making a straight-in landing.  The other traffic in the pattern responded that he would remain clear of the emergency aircraft.  The pilot then executed a successful emergency landing on the runway; with the engine quitting at idle during rollout on the runway.  The aircraft coasted to a stop off the runway on Taxiway 'H' and the passengers and pilot egressed safely.  Subsequent post-flight examination of the engine found a loose fuel line.




Synopsis: The pilot of a V35 Bonanza experienced engine power problems and diverted to a nearby airport. A loose fuel line was identified as the problem.
Date: 201210
Local time of day: 1801-2400
Location: SMO.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: Helicopter
Flight plan: None
Mission: Passenger
Flight phase: Landing
Airspace: Class D SMO
ATC / advisory: Tower SMO
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Environment - Non Weather Related; Aircraft
Primary problem: Ambiguous

Narrative: Loss of GPS reception to a dual set of GARMIN 430/530 receivers while landing at [the building's helicopter] pad. When on the pad; the reception page of the GPS units was referenced and zero satellites were acquired and the strength of reception indicators were zero. [I have] been having this problem sporadically in recent months after three years of never having this problem at this location.




Synopsis: Helicopter pilot reports a loss of GPS signal during landing at a building's helicopter pad. The loss of signal has been occurring sporadically over the last three months with no previous problems detected.
Date: 201705
Local time of day: 0601-1200
Location: ZJX.ARTCC, FL
Flight conditions: IMC
Weather elements / visibility: Thunderstorm; Turbulence
Light: Daylight
Aircraft: Learjet 60
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZXJ
ATC / advisory: Center ZJX
Aircraft component: Weather Radar
Component problem: Failed
Reporter organization: Corporate
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Aircraft; Weather
Primary problem: Weather

Narrative: Over the Gulf of Mexico we encountered severe turbulence. Our radar was working on departure but failed at some point prior to the encounter. When we noticed the radar inop; we asked ZJX Center for 10 miles right based on our storm scope and ZJX Center's radar return. Neither were perfect but all that was available. When the turbulence happened we lost approximately 3;300 ft; bank angle at the most extreme was 45 degrees.




Synopsis: Learjet 60 First Officer reported an encounter with severe turbulence at FL400 resulted in an uncommanded 45 degree bank and loss of 3300 ft.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Flight phase: Takeoff / Launch
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter function: observer
Human factors: Situational Awareness; Time Pressure; Troubleshooting
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Observer
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Two aircraft of the same make; one orbiting ZZZ; second [aircraft] departing NW. From Ground; [they] appear to not see each other. Near miss. Should check ATC radar tapes; and Audio Tapes.




Synopsis: An Observer at the airport witnessed a NMAC between two similar aircraft; one circling and the other taking off.
Date: 202009
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Incorrect / Not Installed / Unavailable Part; Environment - Non Weather Related; Company Policy
Primary problem: Ambiguous

Narrative: During arriving Flight ABCD; ZZZ1-ZZZ; the ramp crew had approximately 20 gate checked bags that needed to be delivered to the passengers in the jet bridge.  Large numbers of gate checked bags are a constant when dealing with flights utilizing the X type of aircraft.  In ZZZ; the vast majority of these flights were sent to Terminal X; where most of the jet bridges are furnished with conveyor belts allowing for safe delivery of the bags to the passengers.  Since Terminal X is closed due to the COVID-19 pandemic; these returning aircraft are being sent to Terminal Y where there are not nearly as many jet bridges furnished with said conveyor belts.  Such was the case with Flight ABCD.  The ramp crew needed to walk the baggage up the jet bridge stairs.  Mostly one at a time as this allowed them to maintain a grip on the handrail.  Even though it was the safest way; it puts tremendous strain as they needed to walk up and down approximately 14 steps about twenty times.  The only ways to avoid this is to take two bags at a time; which increases exposure to a fall; hand the bags up to the landing from the ground level; which makes the agent reach repeatedly into the red zone; thus putting them at risk; or use a belt loader to act as a conveyor to the landing; which it isn't designed for.




Synopsis: Ramp worker reported that an inadequate number of conveyor belts at a terminal resulted in ramp crew hand-carrying baggage up jet bridge stairs repeatedly; exposing them to multiple safety risks.
Date: 202002
Location: LCCC.ARTCC, FO
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Situational Awareness; Distraction; Confusion; Workload
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Just as we reached our initial cruise altitude at FL300 we experienced approximately 5 minutes of GPS interference. We were west of TLV and south of Cyprus at position N33 E033.




Synopsis: Air carrier Captain reported possible GPS jamming.
Date: 201212
Local time of day: 0601-1200
Location: TEB.Airport, NJ
Light: Daylight
Aircraft: Learjet 40
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B EWR; Class D TEB
ATC / advisory: TRACON N90
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Other / Unknown
Anomaly: Deviation - Altitude Crossing Restriction Not Met; 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; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure; Airspace Structure
Primary problem: Human Factors

Narrative: [We] departed Runway 24 off of Teterboro on the RUUDY FOUR RNAV Departure. Crew had briefed the departure and noted WENTZ at 1;500 FT then TASCA at 2;000. We had set 2;000 in the ALT Select on the aircraft. We took off and passed WENTZ above 1;500 FT then continued to 2;000 FT before TASCA. At this point ATC asked us which departure we where on; we replied with the RUUDY FOUR. Then ATC advised us we where not supposed to be [above 1;500 until we are past] WENTZ because of Newark departures. We realized at that point we climbed past 1;500 FT too soon. We realized we need to look at the departure independently and always set the initial altitude in the altitude selector.




Synopsis: LR40 Captain reports exceeding 1;500 FT prior to WENTZ on the RUUDY 4 departure from TEB. ATC notes the error.
Date: 201209
Local time of day: 0001-0600
Location: RPLC.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Tower RPLC
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Engineer
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We] taxied to Runway 20L from base of Tower. Out F5; [we] missed left turn on A. No signage at all on airport for taxiways and runways. No other aircraft around. Ground Control just directed us then on 20R to proceed to 20L. First Officer went 'heads down' for a moment. Field was unfamiliar to us and much less sophisticated than all other international airports we use. Next time; I'll make myself more familiar with the unmarked taxiways. It sure would help if the airport would go to the effort to put signs/markings in place.




Synopsis: RPLC has no runway or taxiway signage so after a flight crew missed the turn from Taxiway F5 onto Taxiway A they were directed to taxi on Runway 20R.
Date: 201904
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: We reported fuel truck numbers XX53; X41; X38; and X04 to [Supervisor] at [Company] with the concern of leaking fuel and oil on the ramp. [Three months later] we reported truck numbers X37; X43; X18; X14 and X04 with the same issues. [Two days later] we reported truck numbers XX26; XX98; XX53; XX69 and X18 also with the same issues. [Three weeks later] these trucks are being reported as well: XX69; X18; X43; and X41. This is an ongoing slip and fall hazard as well as an Environmental Protection Agency issue.




Synopsis: Air carrier ramp personnel reported numerous fuel trucks leaking fuel and oil on the ramp creating an environmental hazard as well as a safety issue.
Date: 201411
Local time of day: 1201-1800
Location: MSP.Airport, MN
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: Our flight was cleared to taxi from the 30R de-ice pad via taxiway P left C and hold short of RWY 12R on C. The taxiways; markings; lines and hold short lines were obscured by fresh snow and the visibility was affected by -SN. Additionally; the taxiways were slippery and given the time of day; dusk was starting. During taxi on taxiway C; ground control was also communicating with another air carrier [with similar call sign] which confused me and misinterpreted this as a crossing clearance for 12R. When I realized this message was not intended for our flight I slowed down and tried to determine my position exactly. It was at this time that I discovered that my nose wheel had indeed crossed the (obscured) hold short line. Additionally I received a very clear caution from the runway status lights. I brought the airplane to an immediate stop and had my First Officer notify the tower. An airplane on short final was instructed to go-around. We received further taxi instructions to proceed to RWY 17.  A very important factor that led to this incursion is the Company policy to assign very similar sounding call signs to simultaneously operating flights in the same airspace. Although my situational awareness was impeded by meteorological factors; I am convinced that this event would not have taken place if I would not been confused by the similar sounding call-sign over the same frequency.




Synopsis: CRJ-200 Captain reported a runway excursion resulted when he mistakenly took a clearance intended for another company aircraft with a similar call sign.
Date: 201903
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The aircraft took off from ZZZ. [As] we passed 10;000 feet; I started tasting something like metal in my mouth about this time the flight deck called and said we were turning around to go back to ZZZ because they smell something unknown and they had to don the oxygen mask. By this time; the crew was starting to get some symptoms; we took our jump seats and landed back in ZZZ. The aircraft was met by EMTs and airport police. They took us to different emergency rooms. At the emergency room; they gave me oxygen and did the carbon monoxide test.




Synopsis: Flight Attendant reported unknown odor during climb. Simultaneously; the Captain reported a return to departure airport due to unknown odor.
Date: 201808
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: McDonnell Douglas Helicopter Undifferentiated or Other Model
Operator: Air Taxi
Operating under: Part 135
Flight plan: VFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Cockpit Canopy Window
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Rotorcraft
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Bird / Animal
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: After departure; level 500 MSL/AGL; bird came through right front window. Debris hit pilot and front two passengers. Passenger #2 (by doorway) had pieces of bird and Plexiglass hit his face and his glasses; as he put it; 'exploded off of my face.' I looked down and saw Passenger #1 (front middle seat by me as the pilot) holding a piece of Plexiglass in her hand and bleeding. I radioed the Tower and advised of the bird strike and that I was immediately returning to base (about 3 miles) since the aircraft didn't seem to be damaged except for a hole in the windshield. We returned to base with no issues with airworthiness and Passenger #1 was bleeding; so I wanted to get her medical attention as soon as possible. The bleeding [turned out] being very minor after we landed. She said her injury was only a scratch so self-diagnosed herself. Airport medical came and looked at her and she confirmed that she was fine. The hole in the right front window was approximately 20' x 24' and ZZZ wildlife officer came out and took blood and feather samples to determine the exact type of bird it was.




Synopsis: Helicopter pilot reported a large bird struck the aircraft shattering the canopy.
Date: 201203
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: King Air C90 E90
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I called TRACON for two departure releases. The first was a CJ1 departing Runway XX on the SID which is a left downwind departure and was released. I then requested release on the BE9; Runway XX second departure which is straight out to the northwest. I said we would provide visual separation between him and the CJ1. As I was saying the last part of my request the TRACON Controller started to say 'Hold for Release.' As I finished my request; all I heard from the TRACON Controller was 'Release;' and his initials. I gave my initials and coordinated the visual separation and release with the Local Controller; who then cleared the BE9 for takeoff. A couple minutes later; the Controller at the neighboring airport called to release the BE9; but the Ground Controller said he was already airborne. Order 7110.65; refers to the phraseology 'Hold for Release.' Better phraseology and a better operating practice is to either use the word 'HOLD' or 'RELEASED.' That phraseology would have made this a non-event; because you cannot mistake the word 'HOLD' for 'RELEASED;' but it is certainly possible for a Controller to say 'Hold For Release;' and the other Controller to only hear released. That has happened many times at this facility alone. Granted; I need to listen better; or repeat the instructions back to the originating Controller. The other Controller should not interrupt; because important information can be missed; as in this case.




Synopsis: Tower Controller described an inadvertent release of an IFR aircraft when the TRACON's 'hold for release' was interpreted as released; the reporter suggested a phraseology change.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Landing
ATC / advisory: Tower ZZZ
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: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Landing turbulence short final; 90 wind shift added 5 knots to speed in a very light MD 11; in the flare got higher rate of decent I added power which caused me to land long. I touched down just beyond first third of runway. Touch was smooth low G. Rollout med brakes and was able to exit runway on taxiway.Adding power to arrest rate of descent. Add less power or elect to go around.


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


Synopsis: MD-11 flight crew reported they landed past the first third of the runway due to a wind shift; power application and light aircraft but were able to turn off before the runway end.