elihoole/asrs-aviation-reports huggingface dataset:
Date: 201901
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon arrival only one (1) CFR (Crash; Fire; Rescue) vehicle was in operation. Second; and third large CFR trucks appear not to be serviceable. Two smaller CFR trucks (red) were not started; or in operation. Only 3 CFR personnel were on the field and were in the only running truck. Do not believe this small contingent; and single working CFR vehicle; would be sufficient in an incident. Was told the other vehicles were not in operation due to lack of manning.




Synopsis: B737 Captain reported lack of emergency equipment at airport.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Aircraft: Cessna 152
Operator: FBO
Operating under: Other Part 141
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Normal Brake System
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Distraction; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing on the Runway XXL in ZZZ with my student; the aircraft lost the hydraulic braking system on the right side; unable to stop the plane to keep the center line of the runway. I cut the mixture to stop the airplane and getting into the grass next to Taxiway Delta on the left. Finally the incident was reported to ground control on 120.45 who assisted me all the time; there were no damages.




Synopsis: Cessna 152 flight instructor reported a loss of hydraulic brake pressure after landing; resulting in a runway excursion.
Date: 201201
Local time of day: 1801-2400
Location: DTW.Airport, MI
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground DTW
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Airport; Procedure
Primary problem: Human Factors

Narrative: It had just become nighttime. Detroit uses Runway 9L as a taxiway. We were taxiing on 9L with the pre-takeoff briefing complete. Instructed to exit left on Taxiway M on our way to depart 21R. The Captain said something to the effect of 'I need to make sure not to miss Mike.' Just then I looked to the left and saw we were passing Mike. I said 'Stop.' We MIGHT have been able to slam on the brakes at that time and make a 110 degree turn onto Mike; but instead the Captain brought the aircraft to a non-abrupt stop SHORT of active Runway 21R. I informed Ground that we had overshot Mike but were holding short of 21R. No aircraft was in the takeoff phase at that time. Ground directed [us] onto 21R to make a U turn; then right turn onto Mike to continue for uneventful takeoff on 21R. At NO TIME did we encroach on Runway 21R. The biggest threat would be non-standard markings. Runway 9L is being used as a taxiway yet there is no hold short line on 9L to notify the crew that the next intersection is a runway; NOT a taxiway. As I am not assigned a lot of DTW flying; I am not sure if there might be some hold short lighting that might not have been working at the time; but such markings and lighting would be an extra help to any crew. Be hyper-aware while taxing on 9L. On our next departure; we were assigned the same instructions. I asked for the easy taxi to 22L instead; which was granted. DTW was not terribly busy either time.




Synopsis: First Officer describes using Runway 9L as a taxiway at DTW and missing the left turn on to Mike as cleared. The next intersection is Runway 21R which the crew stops short of although there is no hold short line or signs.
Date: 201709
Local time of day: 0601-1200
Location: ORD.Airport, IL
Flight conditions: VMC
Light: Daylight
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 ORD
ATC / advisory: Tower ORD
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Less Severe; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: On approach to 27L in ORD we had to do a go-around due to the fact that the flight in front of us did not exit the runway in a timely manner. They attempted to ask the controllers if they could exit the runway on 4L but received no response so they had to continue to H1. ATC called our go-around at approximately 100 ft. We accomplished the go-around with a quick right turn out due to traffic departing 28R who were also in a right turn out. We got a quick vector back around to 27L for a visual and landed without incident.




Synopsis: B737 Captain reported they had to go-around due to traffic still on the runway.
Date: 202009
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Guest was noted with a short face shield only during the compliance walk prior to departure. Apologized to guest. Inquired due to policy change if she had a face mask as a shield alone was no longer sufficient. She said she did and was able to don it.Please make everyone happier by catching this prior to boarding. Flight attendants already have tons on [their] plate.




Synopsis: Flight Attendant reported that a passenger was wearing only a face shield and was asked to wear a face mask to be in compliance.
Date: 201603
Local time of day: 1801-2400
Location: P50.TRACON, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E P50
ATC / advisory: TRACON P50
Second aircraft: Aerobatic
Reporter function: Pilot Not Flying; First Officer
Anomaly: Conflict Airborne Conflict
Detector: Automation Aircraft RA; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure
Primary problem: Airspace Structure

Narrative: We were in close proximity to IWA; our intended landing airport.  We were given a heading of approximately 270 and then told by Phoenix approach we had traffic at our 12 o'clock contact IWA tower and cleared for the visual approach.  Immediately after this instruction we received an RA telling us to climb.  The Captain disconnected the autopilot and complied with the original climb order.  I made a radio call to Approach and told them we were responding to an RA.  During the climb we received course reversal commands telling us to then Descend; Descend.   Approach then instructed us to turn right.  After the RA was complied with we reported that we were returning to course and switched over to IWA tower.  I never got visual on the intruding aircraft.  The jumpseater reported seeing the aircraft and said it was very close.  There is a practice area for aerobatic aircraft very close to the approach corridor for IWA.  I believe this practice area should be moved further south to avoid conflicts.

Callback: The reporter states the event occurred near VPREN (visual point renaissance) and was likely caused by rapidly climbing aerobatic aircraft. Reporter is not sure of the location of the aerobatic box that they may have been departing.



Synopsis: Air Carrier First Officer experienced a TCAS RA at 5;000 feet descending east of IWA. The RA changed from a climb to a descend but the aircraft involved was not seen. Reporter believes the aircraft involved was returning from an aerobatic practice box.
Date: 201706
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Leading Edge Flap
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During flap retraction on takeoff; the LE FLAPS TRANSIT light on the forward panel illuminated accompanied by all LE devices in transit on the overhead panel. Looking out the window; the devices were stuck out. We coordinated a slow climb at 210 - 220 KIAS to FL200 while complying with SID and ATC instructions. We referenced the QRH and contacted Dispatch and Maintenance. Initially; we considered [an alternate airport] for the diversion but the weather was raining with TCU and rain bands approaching from the south due to the tropical depression in the southeast. [A second alternate] was dry and clear. We were heading to (gulf coast city) with (another gulf coast city) as an alternate due to same weather system. We decided to burn gas in holding and land at [the second alternate] due to our heavy weight. While holding; we extended the flaps to 15 and the LE devices still were stuck with Number 8 in the green now. Our goal was to get the aircraft weight under 124;000 pounds to prevent a wheel fuse plug melt. While in holding at approximately 126;000 pounds; all LE devices extended and remained green. This reduced our approach speed to allow an uneventful flaps 15 landing. On taxi in; Maintenance advised to try and raise the flap and flap handle as part of normal after landing flow. The LE devices remained extended.




Synopsis: B737-700 Captain reported diverting to an alternate airport due to a leading edge flap anomaly.
Date: 202112
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Pneumatic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Troubleshooting; Workload; Distraction; Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Result: Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On Date; the flight [was] from ZZZ to ZZZ1. Once we decided to push back; we started Engine 1 and on completing the push back; we started our Engine 2. After the engine start; we moved to our normal procedure which is to transfer the packs to the engine bleeds and shutdown the APU. As we did; we immediately began to hear an extremely loud noise followed by a very strong smell. The noise was overwhelming; I could barely communicate with the First Officer; I could not hear my radio and neither could my First Officer. I could not communicate with my Flight Attendant. We decided to change the packs and bleeds configuration multiple ways but the noise and smell were only getting worse so we decided to return to the gate. As we returned to the gate we messaged Dispatch; however; we did not receive any reply. We proceeded to perform our normal shutdown checklist and the noise only went away once the avionics master switches were off. Once we were able to resolve the issue we immediately called Dispatch to report the situation. The Flight Attendant and the passengers were also able to hear the noise and observed the strong smell. Maintenance came and resolved the issue. After that we were able to resume our flight; no further issues noted.A lack of communication caused by a maintenance issue that brought an overwhelming loud noise followed by a strong smell requiring an immediate action. I took the steps necessary to make sure the passengers were safe and get the issue quickly resolved.




Synopsis: Air carrier pilot reported a loud noise while at the gate and during taxi; the noise continued along with an odor throughout the cabin. The crew returned to the gate for maintenance.
Date: 201710
Local time of day: 0001-0600
Location: ZKC.ARTCC, KS
Flight conditions: Mixed
Weather elements / visibility: Rain; Icing; Snow; 10
Light: Night
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZKC
ATC / advisory: Center ZKC
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action; General Flight Cancelled / Delayed
Contributing factors: Weather
Primary problem: Weather

Narrative: I was on a solo flight and the temperatures were near freezing (2C). I was flying at 6000 ft. The conditions were VFR BKN 20;000 so good visibility. I was on an IFR flight plan so I was in contact with KC Center. Everything was smooth. I looked off to the left and noticed the strobe lights reflecting some precipitation. I turned on my landing light and saw rain/sleet/flurries coming at me. So I called ATC and asked for lower. I went down to 4000 ft. The precipitation was still coming and I asked for lower again; so I went down to 3000 ft. At this point ATC LOST RADAR CONTACT because I was too low. The precip was still there and I wasn't going to go any lower. So I started thinking about either turning around or diverting. Fortunately Effingham's city lights were right in front of me. I definitely had to make some quick decisions. I called up ATC; requested a diversion. Moments later after I requested to divert the precip intensified and it felt like I was in a blizzard. The visibility dropped rapidly from like 10nm to 3nm and the precip increased. In retrospect I believe I hit a small cell. But anyways the precip was increasing and the visibility decreasing; I asked ATC for vectors but they couldn't give any because of the size of the airport so I ended up doing the GPS 11 approach. The ATC controller wanted me to do the full procedure; but in that situation I didn't have time to stay out and accumulate icing; so I turned for the FAF (final approach fix) and told the controller. The controller cleared me for the approach and then I had a normal landing.




Synopsis: A C172 pilot reported encountering rain; sleet; and icing enroute. He made some quick decisions that included diverting to exit the weather and a modified instrument approach to minimize his time in the icing.
Date: 202101
Local time of day: 1801-2400
Location: MMMX.Airport, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower MMMX
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; 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: Airport; Human Factors; Procedure
Primary problem: Airport

Narrative: Landed and began to exit high speed Taxiway E when Tower said turn left onto EG.  Saw no signage for EG.  Pilot Flying then said 'Can't make that taxiway' because of the Tower distraction.  Then Tower said to exit right onto Taxiway Golf and hold short of  [Runway] 05R.  When holding short of 05R on Hotel; Tower said to cross 05L at B.  Informed Tower we were short of 05R at Hotel.  Was asked if we could cross 05R at Bravo.  We proceeded to cross 05R but saw no signage for Taxiway B; then [we] were told to turn left onto H1 and hold short of 05L at Bravo.  Crossed Runway 05L and proceeded to the gate. [Caused by] lack of signage and poor runway lighting.  Also Tower interrupting when rolling out to exit the runway. [Suggest] better signage and lighting and Tower giving better communication not during landing.




Synopsis: First Officer reported some confusion regarding their taxi clearance after landing at Mexico City because of poor signage and lighting.
Date: 201807
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Light wind; 10
Light: Daylight
Aircraft: Sail Plane
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Landing Gear
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Workload; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Procedure; Aircraft
Primary problem: Human Factors

Narrative: Motorglider entered pattern on 45. On 45 I began checklist USTALL; Undercarriage; Switch; Trim; Airbrake; Look; Land as used in pure gliders. The student has [a condition] but drives and is high functioning. His characteristic that distracted me in doing the checklist was making requests. I had just discussed the first landing checklist item of undercarriage when he requested to land engine-off. The gear did not get put down and I began procedure for engine off by setting timer for the prescribed 1 minute at 3;000 RPM but when shutting off magnetos; magneto A did not respond so engine continued running despite magneto A being in OFF position and throttle at idle. Therefore unable to feather prop in horizontal position.Student made another request that he fly final to landing and the gear alarm was not recognized. The gear alarm activates when gear is up and spoiler is unlocked. The gear alarm was only heard upon exiting the aircraft after skidding 150 feet. Checklist was on my lap.Recommendation is to help Instructors deal with [certain conditions] with more information dissemination of appropriate sorts.




Synopsis: A motorglider pilot reported that due to distraction the landing gear was never deployed during landing.
Date: 201503
Local time of day: 1201-1800
Location: SFO.Tower, CA
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Flight phase: Landing
Airspace: Class B NCT
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict NMAC
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The first officer was flying an FMS bridge visual to runway 28R when TCAS alerted us to traffic immediately followed by an RA monitor vertical speed. The ADI aircraft position was above the red threat area as the first officer continued to comply with RA as I searched for traffic. I observed a Cessna 172 at aircraft position 2 o'clock in close proximity that quickly passed underneath us. The first officer; jumpseat pilot; and I observed that TCAS indicated a miss of 400 ft. After the Cessna 172 passed the TCAS announced clear of conflict and the first officer continued the approach to an uneventful landing. The entire event occurred in less than 2 minutes.




Synopsis: B767 Captain reported an NMAC with a C172 on the FMS Bridge Visual to SFO.
Date: 201201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Nose Gear Tire
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Situational Awareness; Distraction; Time Pressure
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Result: General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: I was helping change a nose tire. I was also wanted on another aircraft as soon as possible. The [nose] axle [nut] outer washer was left off. There was no damage done to the axle. Even though I was not the person who removed and installed the axle nut; I'm the one who signed the job off.


Second narrative: Removed and Replaced (R/R) nose wheel and tire assembly per Maintenance Manual (M/M).


Synopsis: Two Line Mechanics report that a nose gear axle nut washer was not reinstalled on a B767-300 aircraft during a nose tire change at a terminal gate.