elihoole/asrs-aviation-reports huggingface dataset:
Date: 201409
Local time of day: 1201-1800
Location: OGG.Airport, HI
Flight conditions: VMC
Light: Daylight
Aircraft: Caravan 208B
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class C OGG
ATC / advisory: Tower OGG
Second aircraft: B757-200
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Contributing factors: Airport; Procedure; Human Factors
Primary problem: Human Factors

Narrative: We were cleared for Take off on RWY 5; while a B757 who had just landed RWY 2 was instructed to hold short of our runway. The runway was clear as we began our departure roll; however as we began our rotation the B757 continued past the hold short line and into RWY 5. The tower instructed the 757 to 'stop' and he did; with about half of the aircraft across the line. We crossed about 100 feet above him. Had we rotated 1000 feet or more down the runway and/or been a larger aircraft; it would have been a very close call. There was nothing we could have done other than what we did. We did not say anything and nobody said anything us.




Synopsis: C208 Captain departing Runway 5 at OGG experiences a runway incursion by a B757 that had been instructed to hold short of Runway 5 after landing on Runway 2. The reporter is able to takeoff before the intersection and climb above the B757.
Date: 201906
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Load Planning
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Pre-flight; Routine Inspection
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: ZZZ Ramp lead failed to secure the DG (Dangerous Goods) with the required 15 bags. He pushed the flight out then attempted to final 4 times before calling [Load Planning]. When he finally called [Load Planning] he stated he thought he didn't need the 15 bags because the scanner accepted his load plan without the required 15 bags. He seemed to be generally confused as to why the scanner would accept his loading but then stop him from finalizing the flight. I told him nothing has changed and all Hazmat must still be secured with 15 bags.




Synopsis: Air Carrier Load Planner reported informing Ramp Lead of Hazmat configuration requirement for securing Hazmat shipment.
Date: 201811
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
Aircraft component: Cylinder
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial
Human factors: Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft; Airport
Primary problem: Aircraft

Narrative: Cruising at 3;000 feet MSL my wife and I smelled smoke; soon after got a puff of smoke in cockpit. I was not under control from any ATC [facility]. I clicked nearest airport on [my GPS]. ZZZ airport was 3 miles ahead. Over flying the field prior to landing airport had yellow X displayed on runway but asphalt airstrip appeared in good condition. Next airport was 15 miles [away] so I landed on closed airport successfully with no problems. After parking removal of cowl I found front right cylinder cracked around the barrel between cylinder barrel and head. Local authority and neighbor stopped by. They had no problems with my presence and said airport was condemned due to lack of upkeep.




Synopsis: C182 pilot reported landing at a closed airport due to smoke and fumes from an apparent engine failure.
Date: 202005
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
ATC / advisory: Center ZZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing out of ZZZZ to ZZZZ1 we were clear to unrestricted FL340. Empty of cargo we got to cruise level quick. We observed a pressure differential message and a rise 8.5 to 9.2 and up; as well as the cabin altitude rapidly climbing above schedule 7;000 ft quick; 8;000 ft and 9;000 ft at that point I told everybody; ' put the oxygen mask on' and verify the outflow valve. Quickly after that we got the level 3 ' cabin altitude' warning. I pulled the QRH and read to comply with the rest of the procedure for level 3 cabin altitude while the Captain was at the controls and the radios. I selected the cabin pressure on manual and turn the knob slowly and fast and there was no response. Since we had no control of the cabin altitude that kept on climbing; the Captain on the radio requested a descend to 10;000 feet follow by the wads and requested land back in ZZZZ with runway in use and weather. We recycle the air system controller and try the cabin pressure controller knob again no response. Then set on auto for the landing in ZZZZ Runway XXR + 3;000 meters visibility night conditions. After landing I verified the outflow open and pressure differential. We parked on apron. During the flight we were asked by the controller if we where having an emergency; The Captain answered: 'no; but we were experiencing a pressurization problem and we needed to descend'. On the ground the mechanic showed us the lower pressure relief valve stuck clogged with insulation. I am not sure how to prevent this event from occurring again; but next time I get a clearance to climb unrestricted and I am close to another heavy aircraft; climbing on the departure maybe request a vector. But that was the furthest on my mind; because of night flying and terrain the only thing I could think about at that moment was climbing at a good rate.




Synopsis: Pilot reported uncontrollable cabin altitude; resulting in an Air Turn Back and precautionary emergency landing.
Date: 201407
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation III; VI; VII (C650)
Operator: Corporate
Operating under: Part 135
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Other / Unknown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General Declared Emergency
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During our takeoff roll at V1/Vr speed; we experienced an aircraft almost directly in front of our flightpath. We believed it to be the departing training aircraft which departed prior to us which we were told (after the event) had declared an emergency and reversed it's flight path back to the airport environment. The aircraft passed us on our left at an estimated 200-300 FT horizontal distance and 200-300 FT vertical distance. I (PNF-left seat) first saw the approaching aircraft after calling V1/rotate; I looked up and out and visually saw the training aircraft and assumed he saw our departing aircraft for he was not lined up on centerline; but was sidestepped to the left. We did not receive a TA/RA resolution; assuming due to the fact we were still on the squat switch. We continued without altering our departure clearance which was runway heading and a climb to 3;000 FT. We asked for a confirmation of our takeoff clearance with Tower and were told that the aircraft had declared an emergency and reached the airport but was not on Tower frequency and not communicating with Tower.We feel confident the emergency aircraft saw us departing hence his sidestepped position to the runway. Otherwise we feel he would have been on runway centerline attempting a landing to Runway XX; the opposite end of Runway XY. Our best resolution was to continue; although we passed in close proximity; it was obvious our flight paths were not going to intersect and aborting the takeoff above V1/Vr airspeed would actually have been more detrimental to our aircraft. In fact this scenario happened so quickly; we couldn't even collaborate on what was happening until after it happened.




Synopsis: CE650 Captain departing Runway reports an NMAC with a training aircraft returning to land with an emergency on Runway XY. The Tower was not aware of the returning aircraft until after the CE650 had rotated.
Date: 201909
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine Driven Pump
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Regained Aircraft Control
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: My student and I were doing pattern work; and we had done 6 touch and goes including 2 slips; simulated engine failure by pulling power to idle and a Go-around. On our last pattern my student pulled power to 1500 rpm abeam the numbers (RWY XX was the runway we were cleared touch and go) the student put in flaps 10 and then turned base. On the base leg I noticed that the RPM indicator showed 1000 rpm so I asked my student why did you pull the power to idle; then I realized the student had not but the engine had failed and in fact the student had given full power and it was still showing 1000 rpm. So I took the controls and noticed the mixture was rich; fuel selector was on both and the fuel shut off value was in. I pitch for best glide and told tower we had an engine failure and asked to land on runway XY. They said I was cleared to land (I chose that runway because the flaps 10 had already been put in and I was not going to make it to runway XX) before I was lined up for runway XY I put the electrical driven fuel pump on and then the engine started back up. I brought the throttle back and told tower I would just land on runway XX. So we landed runway XX and taxied back to the ramp with the fuel pump on. My guess is the engine driven fuel pump had a problem or there was something that clogged the line. The plane was proper preflight and all the fuel sumps were sumped and there was no sign of water or debris.




Synopsis: C172 Instructor reported engine failure during pattern work with student.
Date: 201604
Local time of day: 1201-1800
Location: LAX.Airport, CA
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground LAX
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Ground Conflict; Critical; Ground Event / Encounter Vehicle
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: Taxiing out at LAX; we were cleared to taxi 'Charlie short of Charlie 6' by ATC. Approaching Charlie 5; a baggage vehicle drove directly in front of us on the vehicle service road; requiring me to apply maximum/full brakes to stop the aircraft from hitting the vehicle. It was a tug vehicle pulling 6-7 flat carts all connected together traveling at a fast rate of speed from our left to right. I immediately notified ATC who responded by calling 'city ops' on the same ground frequency and told them to try to figure out who pulled in front of us. We had cleared all turns and had our taxi light on per SOP and did not see this vehicle approaching at all. We estimate the nose was within 5 feet of the cart when we came to a complete stop. When we resumed taxiing; I had the FO check on the FAs to make sure they and the passengers were ok from the abrupt stop. They said that everyone was ok. We were taxiing around 10 knots when full braking was applied. It appeared that the ground vehicle did not look to see if it was clear to cross taxiway Charlie.




Synopsis: EMB-175 Captain reported having to brake abruptly to avoid a string of bag carts while eastbound on Taxiway C at LAX.
Date: 202107
Location: ZZZ.TRACON, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Situational Awareness; Workload; Time Pressure; Distraction
Anomaly: Conflict NMAC; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft RA; Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Flight took off from ZZZ and at 8;000 feet they had GA traffic in sight. The TCAS went off telling them to descend-they complied. It switched to climb and they did. Crew advised me that flight attendants and passengers were not aware. Crew advised me they were filing the necessary reports.




Synopsis: Air carrier Dispatcher reported one of the assigned aircraft reported a NMAC and the pilot crew would submit the necessary reports.
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Cargo AKE delivered to the aircraft without proper labeling; this AKE was refused transport Flight XXX and was later transported on Flight XXY with proper label. AKE contained DGR (Dangerous Goods Regulations) class 9.




Synopsis: Commercial Airline Ground Agent reported Hazmat shipment in AKE (Cargo container) without proper Dangerous Goods documentation. Agent further stated the shipment was initially refused on earlier flight and subsequently reloaded on next flight without documentation corrections.
Date: 201808
Location: EWR.Airport, NJ
Aircraft: B757 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: Tower EWR
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Situational Awareness; Distraction; Confusion
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Environment - Non Weather Related
Primary problem: Airspace Structure

Narrative: I submitted a [report] about the lights atop the newly rebuilt Goethals bridge on a 3-mile final to the 4s in Newark. At that time they had bright white lights on each pillar in sequence that mimicked REILs. The safety team issued comms to the pilots. Days later the lights were changed to red and flashed on a random pattern.We broke out of a 900 ft overcast the other night and they looked just like REILs again. Flashing white and together. Could easily be mistaken in low visibility conditions.[In the past] we had a mistaken VASI issue on 31 at LGA that almost led to a CFIT incident. This is a similar setup.




Synopsis: B757 Captain reported the lights atop the Goethals Bridge can be mistaken for Runway 4 REILs at EWR.
Date: 201605
Local time of day: 0001-0600
Location: WHP.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Descent
Airspace: Class D WHP
ATC / advisory: Tower WHP
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer
Human factors: Human-Machine Interface; Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Chart Or Publication; Human Factors
Primary problem: Airspace Structure

Narrative: As I approached WHP from the north; the WHP local controller advised me that I had penetrated the BUR Class C airspace in the vicinity of the VPLTW VFR checkpoint. I was using GPS navigation to remain clear of the BUR airspace and argued briefly with the WHP controller. I am certain I was well clear of the airspace; and the radar repeater in the WHP tower has inaccurate overlays. I checked my ground tracks on the 'ForeFlight' application; and the ground track shows me to be clear of the airspace.At the controller's direction; I turned into the rising terrain (from which I maintained visual separation); and proceeded to follow his clearance to approach the airport. After I continued on my base leg pattern entry as directed by the local controller I heard him give me as traffic to another inbound aircraft. I did not hear a clearance to land; and queried the controller and was subsequently cleared to land. I believe this controller deliberately failed to issue landing clearance in an attempt to lure me into landing without clearance.This specific controller has had problems with other pilots at WHP; often attempting to issue flight instruction to inexperienced pilots; and intimidating them as well. I believe he creates a distraction for pilots which compromises safety; and will eventually lead to an accident. I realize that this is not the venue for this vent; and apologize for my frustrated commentary.




Synopsis: A pilot reported that the Tower Controller advised them they penetrated an adjacent Class C airspace. The pilot states according to his GPS and reviewing his route on an aviation software program they did not enter the Class C airspace.
Date: 202010
Local time of day: 0601-1200
Location: ZOB.ARTCC, OH
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Other Training Flight
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
ATC / advisory: CTAF ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Personal
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Situational Awareness; Training / Qualification; Confusion; Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Landing
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Procedure; Human Factors
Primary problem: Human Factors

Narrative: My student and I [were on a] 6 mile visual straight-in approach to ZZZ airport at 2;300 ft. MSL. My student made numerous radio calls reporting our position every 2 miles. We understood there was another aircraft making radio calls in the pattern. The last call reported by Aircraft Y was a left base turn with visual and Sentry ForeFlight contact by us. I asked Aircraft Y if they had us in sight; no response. My student made a final call and we began to enter the runway environment. I could see the notification on my iPad stating there was a target just behind us; same altitude and extremely close. My student landed and while rolling on runway Aircraft Y made a go-around call while flying extremely close and around; slightly above; our aircraft. I replied; 'Appreciate it' and they replied with a confirming double radio click. The other aircraft continued to climb runway heading and we both stayed in the pattern for a few more landings with no other issues until we departed the area to the south.




Synopsis: Flight Instructor reported their student flew in front of another aircraft causing a go around.