Building an AOG timeline a lessor will actually read

An AOG event is not a paragraph. It is a sequence: detection, grounding decision, parts or tooling wait, release, and the flights that never left because of it.

When Content Nesthub prepares an airworthiness evidence brief, we refuse to paste hangar notes into a slide and call it a timeline. Lessors in the region have seen too many of those.

Minimum spine

• Timestamp of the grounding decision and who recorded it
• Linked flight numbers removed or heavily delayed
• Parts or specialist labour waits called out separately from troubleshooting time
• Release to service timestamp with the document reference your coordinator already holds

What we leave out on purpose

We do not write engineering conclusions we are not qualified to sign. We do not smooth missing ferry legs. Open items stay labelled as open so the lessor conversation stays honest.

If your handwritten hangar book is the only AOG source for a week, say so early. The brief can still work; it will simply show provenance clearly instead of pretending the export was complete.