
gradient reads your records, spots what is changing and follows every initiative through. It lets your decision makers focus on setting the direction and deciding.
Workload in the descent is slipping on the 737 since March, on all three bases.
Checks are moving from paper to PDF. That digitizes only the first layer, the data. Everything above it still runs on memory, spreadsheets and email.
Selecting, training, checking and keeping every pilot current: the people your whole operation depends on, supported by five layers of work.
Only the data is partly digital. Follow each layer, from data to execution, and see what gradient adds.
Partly digital: in an average airline of 300 pilots, each pilot is checked several times a year. The reports sit as paper or PDF, in a records system and spreadsheets.
Reads all of it, as it is. Nothing is replaced.
Someone reads everything: EASA, your authority, IATA, manufacturers, incident reports. All of it generic, then passed on by email to everyone, or no one.
Filtered through your airline: what matters, for whom, right now. A short brief with the impact on you, and a suggested action.
Someone exports, pastes and counts, when there is time. A drift from March is found at the October review.
Grades computed after every check, by fleet, base and competency. A drift is flagged while there is time to act.
A fix from memory and a meeting, with little evidence.
A drafted fix with owners, dates and the evidence behind it.
Taken late, on a picture that is weeks old.
Still yours. Now taken early, with the evidence in front of you.
Emails and reminders. Ten minutes of work takes two days, and nobody can show it worked.
Asks, reminders and the measured result, kept on record.
Inside, the reports you already keep. Outside, the pulse check keeps only what touches your fleet and your programme.
Grades are counted after every check, by fleet, base and competency. Groups under 10 are never shown.
The cause is rarely in the data alone. gradient asks the people who know, in the tools they already use.
The head of training is reviewing descent workload on the 737 fleet.
Needed: unstable approaches by month since March, as group totals only. No names, no flight numbers.
Upload to gradient →Takes about five minutes · the link opens only this requestYour head of training approves, edits or declines. Sign-offs and the change assessment sit in the same place.
gradient never decides. It records who did, and why.
It books, reminds and chases until it is done. The next checks show whether it worked.
Example figures.
Captains promoted October to March land hard 2.3× more often than the rest of the fleet.
↻ See the possible initiativeCaptains promoted October to March land hard 2.3× more often than the rest of the fleet.
Possible initiativeFour extra landing sectors with a line training captain, and a flare session at the next simulator check.
The safety review board sent training a flight-data trend: more high-energy approaches since spring.
↻ See the possible initiativeThe safety review board sent training a flight-data trend: more high-energy approaches since spring.
Possible initiativeA high-energy scenario in the next simulator cycle, briefed to every 737 crew. Decide now; add Base B at the three-month check.
Examiners at one base grade manual flying a grade above the other five.
↻ See the possible initiativeExaminers at one base grade manual flying a grade above the other five.
Possible initiativeOne standardisation day: everyone sees the spread of grades, agrees the standard, then grades again.
Crews back from the winter break score lower at their first check. Three needed a repeat last April.
↻ See the possible initiativeCrews back from the winter break score lower at their first check. Three needed a repeat last April.
Possible initiativeA refresher session in March for every returning crew. Plan the 38 now; add the two when their dates are set.
The authority wants proof that last year’s corrective action on stabilised approaches worked.
↻ See the possible initiativeThe authority wants proof that last year’s corrective action on stabilised approaches worked.
Possible initiativeSend the pack now with the effect measured, and note the e-learning records as following on a date.
This year’s checks and line observations point to the same two weak areas: manual flying after an automation failure, and crosswind landings.
↻ See the possible initiativeThis year’s checks and line observations point to the same two weak areas: manual flying after an automation failure, and crosswind landings.
Possible initiativeBuild next year’s recurrent programme around those two areas, with the evidence attached for the authority.
| OPC_737_B2_0412.pdf | 12 Apr |
| LPC_737_A1_0419.pdf | 19 Apr |
| OPC_737_C3_0502.pdf | 2 May |
| and 61 more files |
“I found 3 documents that mention 737 workload: a training memo from 2024, a meeting note and a slide deck. Here is a summary of each.”
Takes from records systemsEvery check, kept safely and by the rules.
Builds on topgradient reads those checks together, sees a trend across bases, and follows the fix through.
Takes from AI assistantsAnswers in seconds, in plain language.
Builds on topgradient knows your fleets, bases and programme, and keeps track between questions.
Takes from consultantsExperience from many airlines and a clear view of what works.
Builds on topgradient is there after every check, on your own data, long after a project would end.
From pilot training and airline strategy, at a European full-service carrier.
