elihoole/asrs-aviation-reports huggingface dataset:
Date: 201209
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
ATC / advisory: UNICOM ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Trainee
Reporter qualification: Flight Crew Private
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Ground Event / Encounter Vehicle
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The Breezy aircraft involved is a two place experimental tandem aircraft which qualifies as a Light Sport Aircraft. The engine is in a pusher configuration. The pilots sit forward of the wing leading edge with the seats approximately 2.5 inches above the ground. There is no cockpit enclosure. The purpose of the flight was familiarization and training. I was occupying the front seat and a CFI the rear seat. The weather at the time of the event was clear and winds were calm.I announced our intentions to taxi to the runway on UNICOM as we began our taxi. Prior to taxiing onto the runway I again announced our intentions; on UNICOM; to take off on the runway and remain in left closed traffic. There was no response to either of my transmissions. After a takeoff roll of about 1;000 FT the aircraft broke ground.After liftoff at approximately 20 AGL I saw a vehicle and two individuals on the runway approximately 2;000 FT ahead. They were not visible from the takeoff end of the runway probably due to the configuration of our aircraft. The CFI took control and landed the aircraft. We rolled to a stop about 50 FT from the vehicle.




Synopsis: A student pilot and his instructor took of in their Light Sport Aircraft and sighted a vehicle and two people on the runway and potentially at risk. The instructor pilot took control of the aircraft and landed; rolling to a stop some 50 FT before reaching the obstacles.
Date: 201506
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: A300
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Test Flight / Demonstration
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZZ
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: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: FAR Part 91 Post Maintenance test flight at Airport ZZZZ. Shortly after takeoff at approximately 1;000 FT AFL; cockpit filled with Moderate to Heavy fumes/smoke with acrid oil scent. Level 3 ECAM warnings triggered with multiple main deck cargo smoke sensors activated. Crew and onboard maintenance technicians immediately donned O2 masks. ZZZZ Tower [was notified]; requested immediate landing Runway XY at ZZZZ. Landing completed 14 minutes after takeoff; and after ECAM and QRH procedures followed; Level 3 ECAM warning ceased within 5 minutes. Normal landing and rollout followed; aircraft observed by [ARFF] for Fire/Smoke indications; none noted. Aircraft not evacuated; taxied back to ramp with fire trucks following as a precaution. [Cause] unknown at this time; under maintenance review.


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


Synopsis: A300 flight crew reported the cockpit filled with smoke and fumes shortly after takeoff during a maintenance test flight.
Date: 201710
Local time of day: 0601-1200
Location: EDC.Airport, TX
Flight conditions: Mixed
Weather elements / visibility: Haze / Smoke; 3
Light: Daylight
Aircraft: M-20 K (231) / Encore
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E AUS
ATC / advisory: TRACON AUS
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Time Pressure; Confusion; Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter VFR In IMC; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Weather; Human Factors
Primary problem: Human Factors

Narrative: When ferrying my airplane to EDC I elected to make the short hop VFR. Weather at [departure] was marginal but improving with ceilings 1;100 ft broken being reported by ground before taxiing out. I had been at EDC about 45 minutes earlier in my car and observed that the ceiling was 800 ft at that time. KEDC is class G at the surface so I expected to be able to get in with class G VFR minimums.After takeoff from; the ceiling quickly deteriorated as I got closer to EDC. I elected to press on but soon found myself dangerously low and receiving multiple obstacle alerts from my GPS. Rather than risk hitting an obstacle I executed a climbing turn at a high pitch angle to clear the terrain as quickly as possible. This immediately put me into IMC in class E without a clearance or flight plan. I continued my climb northbound to remain clear of any airspace until I broke out of the clouds around 2;800 ft. I then leveled off and called Austin approach for a popup clearance to execute the RNAV 13 approach into EDC. I received my clearance and completed the remainder of the flight without incident.I should have checked the weather at EDC again immediately before taking off since I knew it was marginal. Calling the AWOS would have informed me that the ceilings were too low to fly VFR. Knowing that; I should have either waited for the clouds to lift; or filed IFR from the outset. My get-there-itis stopped me from making the prudent decision of entering the system.I also waited too long to make the decision to turn around. I should have turned around as soon as it was clear the clouds were starting to lower. I pressed on hoping they would improve which pushed me dangerously low and forcing me to climb in IMC without a clearance. Turning around earlier would have allowed me to get a clearance before entering IMC.




Synopsis: M20 pilot reported flying into IMC conditions while trying to fly beneath a low overcast layer.
Date: 202203
Local time of day: 1201-1800
Location: HIO.Tower, OR
Aircraft: Light Transport; Low Wing; 2 Turboprop Eng
Flight plan: VFR
Flight phase: Descent
Airspace: Class D HIO
ATC / advisory: TRACON P80
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Workload; Troubleshooting; Time Pressure; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Separated Traffic
Contributing factors: Airspace Structure; Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Aircraft X was observed violating the HIO Class D Airspace after departing Starks Twin Oaks Airpark (7S3). The aircraft entered the airspace from the south to about 2 miles south of the airfield. From our control location; I noticed the primary radar return on the STARS; then looked out the window and observed the aircraft out the window. there were several other aircraft in his vicinity and I advised the Local Controller of the airspace violation. Local Controller had to make several traffic calls for the aircraft before Aircraft X finally contacted the Tower over TV Highway approximately 2nm south of the field. The pilot requested to transition northbound through the airspace.There needs to be more communication with 7S3 so that they understand the severity of the issues they are causing by having their aircraft and patrons routinely busting the Class D Airspace.  There needs to be harsher penalties; and more follow up from FSDO so that this stops. It has been going on for more than a year on a routine basis.Do we need to incorporate an LOA with this airfield and HIO? Maybe.The addition of the charted TIMBERS Transition Route may be contributing factor now as well.




Synopsis: ATC Supervisor reported an aircraft entered HIO airspace without a proper clearance. The Supervisor stated this is a continuing problem at this location and some form of communication needs to take place with the personnel at the smaller neighboring airport; 7S3. Per the reporter; air traffic from 7S3 routinely violate the Class D airspace at HIO.
Date: 202109
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Human factors: Time Pressure; Workload; Situational Awareness; Other / Unknown; Distraction
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: Approaching ZZZ approx 30 miles to the south at 10;000 ft speed 250 knots. Received traffic call from ATC reporting aircraft at 12 oclock 9000 ft heading south. While looking for traffic received TCAS caution close 500 feet below and climbing. Caution quickly changed to warning with direction to climb. Executed TCAS procedures climbing over contact. Crew never visually acquired aircraft. Resumed previous clearance at 10;000 ft when called clear. Reported TCAS event to ATC. Be prepared for TCAS events in ZZZ.




Synopsis: Air Carrier pilot reported taking evasive action after receiving a TCAS RA.
Date: 201407
Local time of day: 1201-1800
Location: ORD.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ORD
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Time Pressure; Confusion; Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Airport; Procedure; Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: During taxi in we were told to hold short of Taxiway D and give way to another Air Carrier. When the traffic cleared and we were cleared to the terminal a catering truck came out of almost nowhere; passing a truck at the stop line on the service road; and cut us off so close that the right side of the truck was obscured by the nose of our aircraft. I braked very abruptly and aggressively to avoid a collision. We reported this to Ground Control and were given a number to call the Tower.




Synopsis: An Air Carrier Captain made an abrupt and aggressive stop on ORD Taxiway D to avoid collision with a catering truck driven without regard for other traffic or aircraft.
Date: 201604
Local time of day: 1201-1800
Location: AZO.Airport, MI
Aircraft: Cessna Single Piston Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Taxi
ATC / advisory: Tower AZO
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airport; Chart Or Publication
Primary problem: Airport

Narrative: I was in the Tower for familiarity time. Aircraft X called for a VFR clearance; which was then formulated and issued. After read back; the aircraft requested and received a taxi clearance from the ramp to Runway 5. While the aircraft was taxiing; the three of us in the Tower discussed the proper identifier for [their destination]; since it is a source of confusion with the other [airports in the same city]. When we looked back at the aircraft; approximately 15 seconds later; it was observed holding at runway edge; well past the hold line. The pilot acknowledged his error and was allowed to hold there since he was the only active traffic. A moment later he advised ready for departure and was cleared. When he was switched to departure; he conveyed some sort of apology for the error and then left the frequency.This point on the airport is a well known source of runway incursions. Aircraft taxiing off the ramp in that direction have been inadvertently taxiing across the Runway 5 hold line for years and there have been multiple (dozens?) of incursions there. Incursions have involved a varied mix of experience; professional pilots; hobbyists; fixed-wing; and helicopters. The intersection has been heavily modified to prevent errors including twice reconstructing the intersection to make it less confusing; adding runway identification pavement markings; and installing runway guard lights. The hold point used to be identified as an airport Hot Spot on the diagram; but that was removed after the latest reconstruction project was completed last fall. I don't have a recommendation to make; I'm out of ideas.




Synopsis: AZO Tower Controller reported a Cessna aircraft held short of Runway 5; but across the hold short line. The reporter states this is a recurring problem at this location.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Airbus Industrie Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Passenger
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon gate arrival at destination ZZZ; I was informed by the Flight Attendant that a passenger asked for water; and was given a full large bottle of water. Unbeknownst to the Flight Attendant; that bottle was reportedly full to capacity with straight clear grain alcohol; the passenger said. The bottle was transferred into the custody of the Gate Supervisor in ZZZ.




Synopsis: Airbus Captain reported that water bottle given to passenger was actually filled with alcohol.
Date: 201908
Local time of day: 1201-1800
Location: UNV.Airport, US
Flight conditions: IMC
Weather elements / visibility: Thunderstorm; Turbulence
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class D UNV; Class E ZNY
ATC / advisory: Center ZNY
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Regained Aircraft Control
Contributing factors: Weather
Primary problem: Weather

Narrative: Took off from UNV Runway 6 with showers in the area. Above 2;600 ft. began a right turn. Radar began to paint moderate to severe echoes along the course line. Asked ATC for 5 degree left deviation and went IMC. Asked for an additional 15 degrees left. The plan was to return back to the right to the south east of the weather. Prior to turning right the radar began to depict moderate to severe echoes. Turbulence and rain began to intensify. Began to slow to 250 kts. Autopilot failed. Asked ATC for best action to exit weather. ATC assigned heading 360. In the turn heavy rain and severe turbulence began. Experienced a white flash off the nose accompanied by a faint electrical burning smell lasted approximately 30 seconds. While in the turn to 360 aircraft over banked up to 45 degrees multiple times with Pilot Flying counteracting the bank. Experienced 500 ft. altitude gain. Within approximately 1 minute from established on the 360 heading we exited to VMC. FA (Flight Attendant) called asking about the smell. During the event ATC was busy and very hard to get assistance from. The frequency was congested and the Controller seemed hesitant to allow deviations. After the flight the 360 heading from the controller shows not a good route. Prior to departure crew checked weather and the radar depicted light precipitation with scattered areas of moderate. It appears cells formed and intensified after during departure. In response; we slowed the aircraft asked for vectors. We used the equipment provided and followed SOPs which determined our route was ok. Quickly changing conditions were not detected after departure.


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


Synopsis: ERJ-145 flight crew reported severe weather and possible lightning strike during initial climb.
Date: 201202
Local time of day: 1201-1800
Location: TEB.Airport, NJ
Flight conditions: VMC
Light: Daylight
Aircraft: HS 125 Series 700
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B EWR; Class D TEB
ATC / advisory: TRACON N90
Aircraft component: Compass (HSI/ETC)
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface; Confusion; Distraction
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were given the TEB8 Departure. We took off; leveled at 1;500 FT on 240 degree heading in FMS mode. Unsure of why Controller asked; 'are you in the turn yet?' I checked compass heading was off approximately 20 degrees difference between the 2 systems. I turned aircraft to 280 degrees heading and climbed to 2;000 FT. No further problems during flight. Not instructed to contact ATC or given a phone number to call upon landing. Just wanted to make sure there was no problem with New York Departure.




Synopsis: An HS125-700 compass system malfunctioned after takeoff on the TEB 8 SID. Consequently the pilot failed to turn to the 280 heading until after an ATC alert.
Date: 201911
Local time of day: 0601-1200
Location: EWR.Airport, NJ
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B EWR
ATC / advisory: TRACON N90
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Workload; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Weather; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: While receiving vectors for final approach to EWR ILS 22L; we requested speed reduction from 250 knots within 5 miles of final approach course at TEB. We were assigned descent to 3;000 feet; slow to 210 knots and heading 160 to join the localizer only. We believe a second assignment to heading 200 degrees to join was blocked and was not heard by us. ATC queried our heading to join and informed us that we had been assigned 200 degrees to join and to now fly 190 knots or greater; but localizer only. No approach clearance. We were unable to get onto the frequency to request lower until after a full dot high of GS. We were finally cleared for approach from well above with a tailwind. The approach was completed within stable approach criteria but we were turned late; slowed late and descended and cleared for approach late. This caused increased difficulty in flying the approach. We both never heard the 200 degree turn to join which was questioned.




Synopsis: B737 pilot reported a congested ATC frequency and receiving late descent; late turn to final approach course; and late clearance to slow airspeed during vectors to ILS at Newark.
Date: 202008
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Gate Agent / CSR
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Ground Personnel
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: While boarding flight; a toddler who was being carried by her mother put her hand on the top of the gate podium plexi-glass; and the glass came loose and fell.  Luckily I was right there and able to catch the sheet of plexi-glass before it struck the mother or child. This could have caused injury.




Synopsis: Customer Service employee reported having to catch the plexi-glass sheet from the podium after it became loose from it being touched by a toddler in the arms of an adult.